Twitter/X

Hasan (@hasantoxr) wrote on 2026-06-25 that “the best developer tools do not feel…

Brief

OpenTag is an open-source v0 from Monica Cheng (@MeredithCheng22) that lets AI agents be tagged directly in GitHub and Slack threads. It converts mentions into normalized events routed to bound local runners, preserving event metadata, state transitions, repo bindings, isolated branches, callbacks, leases, and audit history; the project (github.com/amplifthq/opentag) seeks stars and community feedback.

Why it matters

Hasan (@hasantoxr) wrote on 2026-06-25 that “the best developer tools do not feel like tools, they feel like your workflow got smarter overnight,” and endorses OpenTag’s aim to have agents run inside GitHub and Slack while retaining event metadata and tracking state transitions.

Key details

  • OpenTag, announced by Monica Cheng (@MeredithCheng22) as an open-source v0 (github.com/amplifthq/opentag), implements an auditable dispatch layer where a mention becomes a normalized event routed to an explicitly bound local runner; it includes repo bindings, local execution, isolated branches, callbacks, leases, audit history, and interchangeable agent runtimes, and the project is soliciting stars and feedback.
Source evidence

The best developer tools do not feel like tools, they feel like your workflow got smarter overnight.

OpenTag is trying to do that for agents: run inside GitHub and Slack, retain event metadata, track state transitions.

Still early. But the idea is right.

Monica Cheng (@MeredithCheng22)

We’ve been working on something new: OpenTag 🔥 open-source @ agent mentions for GitHub, Slack, and beyond.
If the idea resonates with you, a ⭐ would mean a lot:
github.com/amplifthq/opentag

The idea is simple: AI agents should be able to join the work where it already happens.

Instead of copying a GitHub issue, PR, or Slack discussion into another chat window, you should be able to tag an agent directly in the thread, let it work with the right tools and context, and get progress, results, changed files, or even a PR back in the same place.

We built OpenTag around an open, auditable dispatch layer: a mention becomes a normalized event, routed only to an explicitly bound local runner.

This is more than parsing an @ mention. We’re thinking about repo bindings, local execution, isolated branches, callbacks, leases, audit history, and making different agent runtimes interchangeable without hiding what’s happening behind a black box.

OpenTag is still an early v0, but we’re sharing it now because we want the direction to be shaped in the open.

If you want to help make “tag an agent into the work” an open protocol rather than a closed feature, we’d love your feedback.

Video

— https://nitter.net/MeredithCheng22/status/2069869493992501276#m