Twitter/X

Meredith Cheng (@MeredithCheng22) announced OpenTag on 2026-06-24…

Brief

Meredith Cheng's OpenTag is an open-source v0 (github.com/amplifthq/opentag) that lets developers tag AI agents directly in GitHub, Slack, and other threads so agents can act with proper tools and context and return changes or PRs in-place. It centers on an auditable dispatch layer and features repo bindings, local runners, isolated branches, callbacks, leases, and audit history.

Why it matters

Meredith Cheng (@MeredithCheng22) announced OpenTag on 2026-06-24 (github.com/amplifthq/opentag): an open-source v0 that enables tagging AI agents directly in GitHub, Slack, and other threads so agents can work in-place and return progress, changed files, or pull requests.

Key details

  • OpenTag is built around an open, auditable dispatch layer where a mention becomes a normalized event routed only to an explicitly bound local runner; design elements listed include repo bindings, local execution, isolated branches, callbacks, leases, audit history, and interchangeable agent runtimes, and the project solicits community feedback to shape it as an open protocol.
Source evidence

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