Twitter/X

OpenTag (github.com/amplifthq/opentag) is an open-source v0 agent-mention system…

2026-06-25 · 16:27 UTC ·@heyshrutimishra ·1 min read

Brief

OpenTag is an open-source protocol and implementation (amplifthq/opentag, v0) that lets you tag AI agents into existing Slack and GitHub threads so multiple models can answer side-by-side. It uses a transparent dispatch layer—normalized events routed to bound local runners—with repo bindings, isolated branches, callbacks, leases, and audit logs to avoid vendor lock-in and opaque runtimes.

Why it matters

OpenTag (github.com/amplifthq/opentag) is an open-source v0 agent-mention system promoted by Monica Cheng (@MeredithCheng22) that lets you tag AI models (e.g., Gemini, DeepSeek, GLM, or Claude via Claude Tag) directly in Slack and GitHub threads to run them side-by-side and choose the best model in-place.

Key details

  • OpenTag is built around an auditable dispatch layer that normalizes a mention into an event routed to an explicitly bound local runner, enabling repo bindings, local execution, isolated branches, callbacks, leases, audit history, and returning progress, changed files, or PRs without hiding agent runtimes behind a black box.
Source evidence

Claude Tag gives you Claude. OpenTag gives you all the models.

In one Slack thread you can tag any model you want, Gemini, DeepSeek, GLM, and let them answer side by side. So you stop depending on one company's AI.

You pick the best model for each question, right where the work already happens.

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