convez.ai
MCP ServerIntegração & APIsAvançado
quilin-ai

AgentBridge

quilin-ai/agent-bridge

Ponte local para colaboração bidirecional entre Claude Code e Codex

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor MCP que funciona como ponte local bidirecional entre Claude Code e Codex, permitindo colaboração em tempo real entre os dois agentes dentro da mesma sessão de trabalho. Usa arquitetura de dois processos: um cliente MCP foreground e um daemon persistente em background que gerencia o proxy e estado da ponte.

Instalação

$npx convez-ai quilin-ai/agent-bridge

1 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

Estrelas
434
Forks
69
Acompanhando
4
Saúde
87%
Último commit
há 1 dia
Versão
v0.1.31
Issues abertas
51
Contribuidores
3

Casos de uso

  • Orquestração de múltiplos agentes de IA em uma sessão de desenvolvimento
  • Workflow híbrido integrando Claude Code com Codex
  • Colaboração human-in-the-loop entre agentes especializados

Veredito

Ferramenta especializada e bem arquitetada para desenvolvedores que precisam integrar Claude Code e Codex. Exige conhecimento técnico avançado (Bun, TypeScript, protocolos MCP) e é mais um experimento dirigido que uma solução genérica de orquestração.

README

A tradução para o português deste README ainda está na fila.

AgentBridge

CI License

中文文档

Local bridge for bidirectional communication between Claude Code and Codex inside the same working session.

AgentBridge uses a two-process architecture:

  • bridge.ts is the foreground MCP client started by Claude Code via the AgentBridge plugin
  • daemon.ts is a persistent local background process that owns the Codex app-server proxy and bridge state

When Claude Code closes, the foreground MCP process exits while the background daemon and Codex proxy keep running. When Claude Code starts again, it reconnects automatically with exponential backoff.

What this project is / is not

This project is:

  • A local developer tool for connecting Claude Code and Codex in one workflow
  • A bridge that forwards messages between an MCP channel and the Codex app-server protocol
  • An experimental setup for human-in-the-loop collaboration between multiple agents

This project is not:

  • A hosted service or multi-tenant system
  • A generic orchestration framework for arbitrary agent backends
  • A hardened security boundary between tools you do not trust

Architecture

┌──────────────┐     MCP stdio / plugin     ┌────────────────────┐
│ Claude Code  │ ──────────────────────────▶ │ bridge.ts          │
│ Session      │ ◀──────────────────────────  │ foreground client  │
└──────────────┘                             └─────────┬──────────┘
                                                       │
                                                       │ control WS (:4502)
                                                       ▼
                                             ┌────────────────────┐
                                             │ daemon.ts          │
                                             │ bridge daemon      │
                                             └─────────┬──────────┘
                                                       │
                                     ws://127.0.0.1:4501 proxy
                                                       │
                                                       ▼
                                             ┌────────────────────┐
                                             │ Codex app-server   │
                                             └────────────────────┘

Data flow

DirectionPath
Codex -> Claudedaemon.ts captures agentMessage -> control WS -> bridge.ts -> notifications/claude/channel
Claude -> CodexClaude calls the reply tool -> bridge.ts -> control WS -> daemon.ts -> turn/start injects into the Codex thread

Loop prevention

Each message carries a source field ("claude" or "codex"). The bridge never forwards a message back to its origin.

Prerequisites

DependencyVersionInstall
Bunv1.0+curl -fsSL https://bun.sh/install | bash
Claude Codev2.1.80+npm install -g @anthropic-ai/claude-code
Codex CLIlatestnpm install -g @openai/codex

Note: Bun is required as the runtime for the AgentBridge daemon and plugin server. Node.js alone is not sufficient.

Quick Start

Install via Plugin Marketplace (recommended)

Install AgentBridge directly from Claude Code using the plugin marketplace:

# 1. In Claude Code, add the AgentBridge marketplace
/plugin marketplace add raysonmeng/agent-bridge

# 2. Install the plugin
/plugin install agentbridge@agentbridge

# 3. Reload plugins to activate
/reload-plugins

Then install the CLI tool:

# 4. Install the CLI globally
npm install -g @raysonmeng/agentbridge

# 5. Generate project config (optional)
abg init

# 6. Start Claude Code with AgentBridge channel enabled
abg claude

# 7. Start Codex TUI connected to the bridge (in another terminal)
abg codex

Tip: abg is a short alias for agentbridge. Both commands are identical — use whichever you prefer.

That's it. The daemon starts automatically when needed and reconnects if restarted.

Updating the plugin

When a new version is released, update from Claude Code:

/plugin marketplace update agentbridge
/reload-plugins

Or enable auto-update: run /plugin → Marketplaces tab → select agentbridge → Enable auto-update.

Install for local development

If you want to modify AgentBridge source code, use the local development setup instead:

# 1. Clone and install dependencies
git clone https://github.com/raysonmeng/agent-bridge.git
cd agent-bridge
bun install
bun link

# 2. Set up local plugin + project config
agentbridge dev     # Register local marketplace + install plugin
agentbridge init    # Check dependencies, generate .agentbridge/config.json

# 3. Start Claude Code with AgentBridge plugin loaded
agentbridge claude

# 4. Start Codex TUI connected to the bridge (in another terminal)
agentbridge codex

Note: agentbridge claude injects --dangerously-load-development-channels plugin:agentbridge@agentbridge automatically. This loads a local development channel into Claude Code (currently a Research Preview workflow). Only enable channels and MCP servers you trust.

Updating after code changes

After modifying AgentBridge source code, re-run agentbridge dev to sync changes to the plugin cache, then restart Claude Code or run /reload-plugins in an active session.

CLI Reference

All commands work with both agentbridge and the short alias abg.

CommandDescription
abg initInstall plugin, check dependencies (bun/claude/codex), generate .agentbridge/config.json
abg claude [args...]Start Claude Code with push channel enabled. Runs with --dangerously-skip-permissions by default (opt out: --safe or AGENTBRIDGE_SAFE=1). Clears any killed sentinel from a previous kill. Pass-through args are forwarded to claude
abg codex [args...]Start Codex TUI connected to AgentBridge daemon. Bare abg codex auto-resumes the pair's last thread; use abg codex --new for a fresh thread. TUI launches run with --yolo by default (opt out: --safe or AGENTBRIDGE_SAFE=1; non-TUI subcommands like exec are never touched). Manages TUI process lifecycle (pid tracking, cleanup). Pass-through args forwarded to codex
abg resume [claude|codex]No target: print the resume commands for this directory's last Claude Code session and this pair's current Codex thread. With a target: resume that side directly (delegates to abg claude --resume <id> / abg codex resume-current)
abg pairsList registered pairs; abg pairs rm <name|id> removes one; abg pairs prune previews reclaimable orphan dirs + stranded registry entries (cwd-gone, dead, >1 day), abg pairs prune --apply deletes them
abg doctor [--json]Read-only diagnosis: env, daemon health/readiness, build drift, artifact alignment, TUI attachment, logs
abg budget [--json]Both agents' subscription quota snapshot (5h/weekly windows, drift, pause state)
abg killGracefully stop this pair's daemon and managed Codex TUI, write killed sentinel; abg kill --all stops every pair
abg dev(Dev only) Register local marketplace + force-sync plugin to cache
abg --helpShow help
abg --versionShow version

The pair-aware commands (claude, codex, resume, kill, doctor, budget) accept --pair <name> to target a specific pair — one pair per project directory by default, with ports allocated per pair in +10 strides from 4500.

Owned flags

Some flags are automatically injected and cannot be manually specified:

  • agentbridge claude owns: --channels, --dangerously-load-development-channels
  • agentbridge codex owns: --remote, --enable tui_app_server
  • Both launchers consume the wrapper flag --safe (it is never forwarded): it disables the max-permission defaults for that launch. The defaults are also auto-suppressed when you pass any explicit permission flag yourself (-a/--ask-for-approval/-s/--sandbox for codex; --permission-mode/--allow-dangerously-skip-permissions for claude) — injecting --yolo next to an explicit approval policy is a hard codex CLI conflict.

Passing these flags manually will result in a hard error with guidance to use the native command directly.

Note on flag positioning for agentbridge codex: For the bare TUI form (agentbridge codex …), bridge flags are injected at the front. For TUI subcommands that carry per-subcommand args (resume, fork), they are injected after the subcommand name (so clap parses them as options of the actually-invoked command, not the root). Non-TUI subcommands like exec, mcp, plugin, remote-control, update etc. are passed through unchanged — no bridge flags injected. See src/cli/codex.ts buildCodexArgs for the full positioning logic.

Project Config

Running agentbridge init creates a .agentbridge/ directory in your project root:

FilePurpose
config.jsonMachine-readable project config (Codex ports, turn coordination, idle shutdown)

The config is loaded by the CLI and daemon at startup. Re-running init is idempotent and will not overwrite existing files.

File Structure

agent_bridge/
├── .github/
│   ├── ISSUE_TEMPLATE/           # Bug report and feature request templates
│   ├── pull_request_template.md
│   └── workflows/ci.yml          # GitHub Actions CI
├── assets/                        # Static assets (images, etc.)
├── docs/
│   ├── phase3-spec.md            # Phase 3 design spec (CLI + Plugin)
│   ├── v1-roadmap.md             # v1 feature roadmap
│   └── v2-architecture.md        # v2 multi-agent architecture design
├── plugins/agentbridge/           # Claude Code plugin bundle
│   ├── .claude-plugin/plugin.json
│   ├── commands/init.md
│   ├── hooks/hooks.json
│   ├── scripts/health-check.sh
│   └── server/                    # Bundled bridge-server.js + daemon.js
├── src/
│   ├── bridge.ts                  # Claude foreground MCP client (plugin entry point)
│   ├── daemon.ts                  # Persistent background daemon
│   ├── daemon-client.ts           # WebSocket client for daemon control port
│   ├── daemon-lifecycle.ts        # Shared daemon lifecycle (ensureRunning, kill, startup lock)
│   ├── control-protocol.ts        # Foreground/background control protocol types
│   ├── claude-adapter.ts          # MCP server adapter for Claude Code channels
│   ├── codex-adapter.ts           # Codex app-server WebSocket proxy and message interception
│   ├── config-service.ts          # Project config (.agentbridge/) read/write
│   ├── state-dir.ts               # Platform-aware state directory resolver
│   ├── message-filter.ts          # Smart message filtering (markers, summary buffer)
│   ├── types.ts                   # Shared types
│   ├── cli.ts                     # CLI entry point and command router
│   └── cli/
│       ├── init.ts                # agentbridge init
│       ├── claude.ts              # agentbridge claude
│       ├── codex.ts               # agentbridge codex
│       ├── pairs.ts               # agentbridge pairs (list / rm / prune)
│       ├── doctor.ts              # agentbridge doctor (read-only diagnosis)
│       ├── budget.ts              # agentbridge budget (quota snapshot)
│       ├── kill.ts                # agentbridge kill
│       ├── pkg-root.ts            # package-root resolution helper
│       └── dev.ts                 # agentbridge dev
├── CLAUDE.md                      # Project rules for AI agents
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── README.zh-CN.md
├── SECURITY.md
├── package.json
└── tsconfig.json

Configuration

Environment Variables

VariableDefaultDescription
CODEX_WS_PORT4500Codex app-server WebSocket port
CODEX_PROXY_PORT4501Bridge proxy port for the Codex TUI
AGENTBRIDGE_CONTROL_PORT4502Control port between bridge.ts and daemon.ts
AGENTBRIDGE_LIVENESS_PROBE_TIMEOUT_MS3000Maximum wait for incumbent Claude pong before evicting on contention (issue #68)
AGENTBRIDGE_TURN_WATCHDOG_MS300000Per-turn inactivity watchdog: force-completes a turn after this many ms of app-server silence so a lost turn/completed can't lock injection forever (issue #69)
AGENTBRIDGE_CODEX_TRANSPORTautoHow the daemon reaches the Codex app-server: auto (probe codex app-server --help, use ws:// if supported else fall back to a unix:// socket via a transparent relay), ws (force ws), or unix (force unix socket + relay). For builds that drop ws:// listen support (issue #85)
AGENTBRIDGE_STATE_DIRPlatform defaultState directory for pid, status, logs (macOS: ~/Library/Application Support/agentbridge/, Linux: $XDG_STATE_HOME/agentbridge/)
AGENTBRIDGE_DAEMON_ENTRY./daemon.tsOverride daemon entry point (used by plugin bundles)
NO_UPDATE_NOTIFIERunsetSet to any value to disable the "update available" notice (ecosystem-standard opt-out)
AGENTBRIDGE_NO_UPDATE_NOTIFIERunsetNamespaced opt-out for the update notice (same effect as NO_UPDATE_NOTIFIER)
AGENTBRIDGE_UPDATE_PROMPTunsetSet to 0 to disable the interactive update prompt and keep pure notice-only behavior
AGENTBRIDGE_UPDATE_CHECK_INTERVAL_MS86400000How often abg claude/abg codex may check npm for a newer version (default once/day). The notice is otherwise printed from cache — zero network on most runs

Update notifications

abg claude and abg codex print a one-line notice to stderr when a newer stable AgentBridge is published to npm, e.g.:

⚠ AgentBridge update available: 0.1.6 → 0.1.7
  CLI:    npm install -g @raysonmeng/agentbridge@latest
  Plugin: /plugin marketplace update agentbridge   (then /reload-plugins)

The check is best-effort: the notice is printed from a cached result, the npm check runs at most once per day in the background, and any network/registry failure is silently ignored. On an interactive TTY, a cached update prompts before launch; answering y runs npm install -g @raysonmeng/agentbridge@latest, while N (or no answer within 15 seconds) records that version as dismissed and continues launching. Non-interactive output and CI never prompt, and the notice can be disabled with NO_UPDATE_NOTIFIER=1 or kept notice-only with AGENTBRIDGE_UPDATE_PROMPT=0.

State Directory

The daemon stores runtime state in a platform-aware directory:

PlatformDefault Path
macOS~/Library/Application Support/agentbridge/
Linux$XDG_STATE_HOME/agentbridge/ (fallback: ~/.local/state/agentbridge/)

Contents: daemon.pid, status.json, agentbridge.log, killed (sentinel), startup.lock

Disabled Bridge States

The bridge can enter several dormant states when it cannot accept new MCP replies. Each state surfaces to the agent as an error message (and, for the transient ones, an in-band push notification):

StateCauseRecovery
killedagentbridge kill was run, sentinel file present.Restart Claude Code (agentbridge claude), switch to a new conversation, or run /resume.
rejectedDaemon rejected the connection: another Claude session is already attached.Close the other session, or run agentbridge kill to reset, then agentbridge claude again.
evictedA newer session evicted this one after the incumbent failed a liveness probe (issue #68).Close this session and start a fresh one with agentbridge claude.
probe_in_progressA liveness probe is currently checking the incumbent — contention window. Transient (auto-recovers within DISABLED_RECOVERY_INTERVAL_MS × cap, ~30 s).None needed; the recovery poller reconnects automatically when the slot clears.
auto_recovery_exhaustedThe auto-recovery poller for probe_in_progress ran its full retry budget (6 attempts, ~30 s) without succeeding. Terminal.Retry manually with agentbridge claude.

Current Limitations

  • Only forwards agentMessage items, not intermediate commandExecution, fileChange, or similar events
  • Single Codex thread per pair, no multi-session support within a pair yet
  • Single Claude foreground connection per pair; a new Claude session replaces the previous one
  • Multiple pairs run side-by-side on one machine (one per project directory, per-pair port allocation); Windows is not an officially supported platform yet

Codex git restrictions

Codex runs in a sandboxed environment that blocks all writes to the .git directory. This means Codex cannot run git commit, git push, git pull, git checkout -b, git merge, or any other command that modifies git metadata. Attempting these commands will cause the Codex session to hang indefinitely.

Recommendation: Let Claude Code handle all git operations (branching, committing, pushing, creating PRs). Codex should focus on code changes and report completed work via agentMessage, then Claude Code takes care of the git workflow.

Roadmap

  • v1.x (current): Improve the single-bridge experience without architectural refactoring -- less noise, better turn discipline, and clearer collaboration modes. See docs/v1-roadmap.md.
  • v2 (planned): Introduce the multi-agent foundation -- room-scoped collaboration, stable identity, a formal control protocol, and stronger recovery semantics. See docs/v2-architecture.md.
  • v3+ (longer term): Explore smarter collaboration, richer policies, and more advanced orchestration across runtimes.

How This Project Was Built

This project was built collaboratively by Claude Code (Anthropic) and Codex (OpenAI), communicating through AgentBridge itself -- the very tool they were building together. A human developer coordinated the effort, assigning tasks, reviewing progress, and directing the two agents to work in parallel and review each other's output.

In other words, AgentBridge is its own proof of concept: two AI agents from different providers, connected in real time, shipping code side by side.

Contact

This is my first open-source project! I'd love to connect with anyone interested in multi-agent collaboration, AI tooling, or just building cool things together. Feel free to reach out:

Ver o original no GitHub

Bom para

Relacionados