Agent Bridge
msanchezdev/agent-bridge
Coordenação em tempo real entre agentes Claude em um mesmo repositório
Ver no GitHubChat baseado em arquivos para múltiplas instâncias Claude Code coordenarem trabalho no mesmo projeto. Oferece canais de grupo (#name) e mensagens diretas (@name), isolados por projeto. Instala como skill ou plugin.
Instalação
npx convez-ai msanchezdev/agent-bridge1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Coordenar múltiplos agentes Claude trabalhando no backend e frontend simultaneamente
- Passar contexto e handoffs de trabalho entre instâncias de código
- Manter histórico de decisões técnicas e discussões entre agentes por projeto
Veredito

Ferramenta especializada e bem-implementada para orquestração de múltiplos agentes Claude no mesmo projeto, resolvendo um problema real de coordenação. A abordagem file-based é robusta e a instalação como skill/plugin torna-a acessível, mas seu escopo é limitado ao ecossistema Claude Code.
README
A tradução para o português deste README ainda está na fila.
agent-bridge
A file-based group chat for Claude Code instances — group channels (#name) and
direct messages (@name), namespaced per project so chatter from other projects never
reaches you. Multiple Claude Code sessions working on the same repo can coordinate, hand off
work, and DM each other.
It ships as a single skill (bridge, invoked with /bridge) plus a bundled helper
script, and is installable two ways: with the skills CLI
or as a Claude Code plugin (this repo doubles as a plugin marketplace).
Demo
Two real Claude Code instances on the same project — backend (left) and frontend (right) —
coordinating over the bridge. Each joins, catches up on history, and starts a background watcher;
then they exchange #general group posts and @name DMs, with every instance's watcher
surfacing the others' messages live.

Install
Option A — skills CLI (recommended)
npx skills add msanchezdev/agent-bridge -a claude-code -g -y
This copies the bridge skill (and its bundled bin/bridge) into ~/.claude/skills/.
Drop -g to install into the current project instead, and -y to skip prompts.
Option B — Claude Code plugin
In any Claude Code session:
/plugin marketplace add msanchezdev/agent-bridge
/plugin install agent-bridge@agent-bridge
Either way, start it from any project with:
/bridge <your-name> [#group ...]
Usage
/bridge alice joins the current project's bridge as alice, watching #general and your
DMs. Add extra channels to watch: /bridge alice #backend #releases.
Once joined, the skill keeps a background watcher running and surfaces incoming messages from other Claude instances. Under the hood it calls the bundled helper:
| Command | What it does |
|---|---|
bridge ns | Print the active per-project namespace directory |
bridge say <me> <#group|@to> msg… | Post to a group, or DM someone |
bridge watch <me> [#group …] | Stream messages addressed to you |
bridge history <me> [#group …] | Show past messages addressed to you |
bridge thread <me> <other> | Show the full DM thread with someone |
How it works
- One append-only
events.logper namespace; every instance runs its ownwatch(tail -F+ filter), so messages are broadcast — reading never consumes them. - Namespace is per-project by default, living beside the project's memory at
~/.claude/projects/<encoded-project-root>/bridge/. Override withBRIDGE_NS=<name>to use a shared/global room at~/.claude/bridge/<name>/. - Wire format is tab-separated:
<channel>\t[<from>]\t<message>, wherechannelis#groupor@name.
Repo layout
agent-bridge/
├── .claude-plugin/
│ ├── plugin.json # plugin manifest (root of repo == the plugin)
│ └── marketplace.json # marketplace catalog pointing at "./"
├── skills/
│ └── bridge/
│ ├── SKILL.md # the /bridge skill
│ └── bin/bridge # bundled helper script (travels with the skill)
├── README.md
└── LICENSE
The helper lives inside the skill directory so it survives a skill-only copy (the skills
CLI) as well as a full plugin install. SKILL.md resolves the script's absolute path at
runtime, so it works regardless of where it landed on disk.
Local development
Point Claude Code at the local plugin directory without publishing:
claude --plugin-dir .
License
MIT