# Cc Bridge

> Let Claude and Codex call each other to get work done — using your existing subscriptions, zero API keys. A bidirectional MCP bridge.

- **Type:** MCP server
- **Install:** `agentstack add mcp-gordon-g-star-cc-bridge`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Gordon-G-STAR](https://agentstack.voostack.com/s/gordon-g-star)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Gordon-G-STAR](https://github.com/Gordon-G-STAR)
- **Source:** https://github.com/Gordon-G-STAR/cc-bridge

## Install

```sh
agentstack add mcp-gordon-g-star-cc-bridge
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# cc-bridge

[](https://github.com/Gordon-G-STAR/cc-bridge/actions/workflows/ci.yml)
[](LICENSE)
[](https://www.python.org/downloads/)

cc-bridge 把 Claude 和 Codex 接成一条本地双 agent 流水线:**Claude 规划、审查、定位问题,Codex 实现、跑测试、修复**。你 Claude Max 和 ChatGPT 都付了钱,cc-bridge 让它们各走自己的 CLI 协作,不用 API key。(默认分工如此,反过来也行——Claude 也能实现、Codex 也能审查。)

*(English below)*

## 装

```bash
pip install -e .
cc-bridge install      # 然后重启 Claude 和 Codex
```

也可以用打包好的图形安装器 `cc-bridge-installer`,装完同样重启两个 app。

## 用

在 Claude 里直接说,比如:「设计好这个改动,然后让 Codex 实现并跑测试修到通过」——Claude 规划、Codex 落地,背后会调 `codex_execute`。
在 Codex 里反过来:用 `claude_analyze` 让 Claude 评审改动、定位疑难 bug、做架构权衡。

- `codex_execute(task, project_dir)` — 让 Codex 在项目里干活(改文件、跑测试、修复)
- `claude_analyze(task, project_dir)` — 让 Claude 分析、评审、定位
- `project_dir` 要传**绝对路径**;两个工具都可带 `continue_session=True` 接着上一轮会话。
- 每次调用都回一份**标准化报告**:调用方向、项目、任务、改动文件、下一步建议、耗时。
- 想让改动可控:传 `git_mode="safe"`,改动会被隔离到临时分支、跑完提交并切回原分支,原分支不受影响。
- 需要权限可控、可审计的委派时用 v0.2 的结构化合同工具 `codex_handoff` / `claude_handoff`(申请权限范围 + 验收标准,本地策略重授权)。两类工具对照:

| 工具 | 定位 | 适合 |
| --- | --- | --- |
| `codex_execute` / `claude_analyze` | legacy 自由文本 | 简单任务、快速评审、日常迭代 |
| `codex_handoff` / `claude_handoff` | v0.2 结构化合同 | 需要权限可控 / 可审计的委派 |

> 长任务用**异步** handoff:`codex_handoff_async` / `claude_handoff_async` 立即返回 handoff_id、执行在独立后台进程进行(server/宿主关掉也跑完、不撞 `-32001`),用 `*_handoff_status` / `*_handoff_result` 查、`*_handoff_cancel` 取消。诚实限制:回滚仍是「检测不补」(成功但有改动会标 `detected_but_not_reverted`);异步是 MCP SDK v2 Tasks 之前的临时方案。可运行示例见 [`examples/contracted_handoff_demo/`](examples/contracted_handoff_demo/)。

## 注意

**先说清边界:cc-bridge 是「检测 + 补救」,不是容器沙箱。** 它限定可操作范围、检测越界并标记/记录、部分场景尝试补救;但底层 agent 或系统若绕过限制它拦不住——别拿它替代系统级隔离(容器 / VM / 受限账户)。

默认对方能在那个目录里自动改文件、跑命令,**不会问你**。几道安全带:

- **隔离改动** → 调用时传 `git_mode="safe"`(要求干净的 git 仓库),改动只落在临时分支,原分支不动。
- **不信任的代码** → `CC_BRIDGE_CODEX_SANDBOX=read-only`,或 `CC_BRIDGE_ALLOWED_ROOTS` 限定能动的目录。
- **防递归互调** → v0.2 本地策略默认 `CC_BRIDGE_POLICY_MAX_DEPTH=3`,跨 agent 链路超深一律拒绝。
- **装的时候顺手设好** → `cc-bridge install --allowed-roots  --codex-sandbox read-only --audit-log `。

配置和用法细节见 [`docs/CONFIG.md`](docs/CONFIG.md);真实场景示例见 [`docs/COOKBOOK.md`](docs/COOKBOOK.md)。

---

## English

cc-bridge wires Claude and Codex into a local two-agent pipeline: **Claude plans, reviews, and diagnoses; Codex implements, runs tests, and fixes.** You already pay for Claude Max and ChatGPT — cc-bridge lets them collaborate through their own CLIs, no API keys. (That's the default split; it works the other way too — Claude can implement, Codex can review.)

### Install

```bash
pip install -e .
cc-bridge install      # then restart Claude and Codex
```

Or run the packaged GUI installer `cc-bridge-installer`, then restart both apps.

### Use

In Claude: "design this change, then have Codex implement it and run the tests until they pass" — Claude plans, Codex lands it via `codex_execute`. In Codex: use `claude_analyze` to have Claude review changes, debug, or weigh architecture trade-offs.

- `codex_execute(task, project_dir)` — Codex does the work (edits files, runs tests, fixes)
- `claude_analyze(task, project_dir)` — Claude analyzes / reviews / diagnoses
- `project_dir` must be absolute; both tools take `continue_session=True` to resume the last session.
- Every call returns a **standardized report**: direction, project, task, files changed, next-step suggestion, duration.
- Want changes contained? Pass `git_mode="safe"` — work is isolated on a temp branch, committed there, then the original branch is restored untouched.
- For permission-controlled, auditable delegation use v0.2's structured-contract tools `codex_handoff` / `claude_handoff` (requested scope + acceptance criteria, re-authorized by local policy). Quick guide:

| Tool | What | When |
| --- | --- | --- |
| `codex_execute` / `claude_analyze` | legacy free-text | simple tasks, quick reviews, daily iteration |
| `codex_handoff` / `claude_handoff` | v0.2 structured contract | when you need controlled / auditable scope |

> For long tasks use **async** handoff: `codex_handoff_async` / `claude_handoff_async` return a handoff_id immediately and run in a detached background process (survives the host closing, no `-32001`); poll with `*_handoff_status` / `*_handoff_result`, cancel with `*_handoff_cancel`. Honest limit: rollback is still "detect, not revert" (a successful handoff with changes is marked `detected_but_not_reverted`); async is a stopgap until MCP SDK v2 Tasks. Runnable example: [`examples/contracted_handoff_demo/`](examples/contracted_handoff_demo/).

### Heads up

**Scope first: cc-bridge is "detect + remediate", not a container sandbox.** It fences the reachable range, detects and records boundary violations, and remediates in some cases — but it cannot stop a determined agent or the OS from going around it. Don't use it instead of system-level isolation (container / VM / restricted account).

By default the other agent edits files and runs commands in that directory without asking. A few safety belts:

- **Isolate changes** → pass `git_mode="safe"` (needs a clean git repo); changes land only on a temp branch, original branch untouched.
- **Untrusted code** → `CC_BRIDGE_CODEX_SANDBOX=read-only`, or `CC_BRIDGE_ALLOWED_ROOTS` to fence the reachable dirs.
- **No recursion** → v0.2's local policy defaults to `CC_BRIDGE_POLICY_MAX_DEPTH=3`; over-deep cross-agent chains are refused.
- **Set it at install time** → `cc-bridge install --allowed-roots  --codex-sandbox read-only --audit-log `.

Config & usage details: [`docs/CONFIG.md`](docs/CONFIG.md). Real-world recipes: [`docs/COOKBOOK.md`](docs/COOKBOOK.md).

## License

MIT

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Gordon-G-STAR](https://github.com/Gordon-G-STAR)
- **Source:** [Gordon-G-STAR/cc-bridge](https://github.com/Gordon-G-STAR/cc-bridge)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/mcp-gordon-g-star-cc-bridge
- Seller: https://agentstack.voostack.com/s/gordon-g-star
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.