by SeemSeam
Visible multi-agent CLI workspace for mixing Codex, Claude, Gemini, Kimi, Qwen, Cursor, Copilot, Pi, OpenCode, and other AI coding agents
# Add to your Claude Code skills
git clone https://github.com/SeemSeam/claude_codex_bridgeGuides for using ai agents skills like claude_codex_bridge.
Last scanned: 5/10/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-10T06:32:58.802Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}claude_codex_bridge is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by SeemSeam. Visible multi-agent CLI workspace for mixing Codex, Claude, Gemini, Kimi, Qwen, Cursor, Copilot, Pi, OpenCode, and other AI coding agents. It has 3,075 GitHub stars.
Yes. claude_codex_bridge passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/SeemSeam/claude_codex_bridge" and add it to your Claude Code skills directory (see the Installation section above).
claude_codex_bridge is primarily written in Python. It is open-source under SeemSeam on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh claude_codex_bridge against similar tools.
No comments yet. Be the first to share your thoughts!
Designed around agent parity Visible, controllable multi-agent cooperative TUI workspace
English | 中文
Quick Start · v7 UI · Rich Mode · Configure Agents · Mobile Gateway Alpha · User Guide · Developer Guide
Mix CLIs per agent in .ccb/ccb.config; actual availability depends on the local CLI installation and account access.
New role specification: package skills, memory, and tool dependencies into self-contained Role Packs, then create hot-loadable and removable specialist agents.
| See the work | Mix providers | Keep control |
|---|---|---|
| Every agent is a real terminal with layout control. | Run multiple CLIs concurrently from one command. | Stable background communication for multi-line task orchestration. |
New installs should use the npm package:
npm install -g @seemseam/ccb
After CCB is installed, use CCB's updater:
ccb update
Install or refresh the optional rich media workbench; it bundles verified binaries where possible and installs only the required terminal/media/font dependencies through the platform package manager:
ccb update rich
After rich is enabled, plain ccb opens the rich WezTerm launcher unless it is already running inside a CCB-managed rich WezTerm; use ccb uninstall rich to return to the normal terminal startup.
If npm is not available in your environment, download the matching package from Releases:
tar -xzf ccb-*.tar.gz
cd ccb-*
./install.sh install
Source install is for development or temporary fallback use:
git clone https://github.com/SeemSeam/claude_codex_bridge.git
cd claude_codex_bridge
./install.sh install
Source installs link global ccb / ask back to the checkout. Regular users should prefer the npm package.
Out of the box, run ccb from your project directory. If startup reports that .ccb cannot be created automatically or that the project anchor is missing, create .ccb manually:
mkdir -p .ccb
Create .ccb/ccb.config in your project root. For v7, it is better to understand config from multi-window topology first: [windows] defines tmux windows and agent groups, agent:provider defines which CLI each agent uses, and (worktree) gives an agent its own git worktree.
version = 2
entry_window = "main"
[windows]
main = "main:codex"
work = "worker1:codex(worktree), worker2:claude(worktree)"
review = "reviewer:claude, qa:gemini"
[ui.sidebar]
mode = "every_window"
width = "15%"
bottom_height = 20
agents_height = "50%"
comms_height = "15%"
tips_height = "35%"
comms_limit = 3
If you are not sure how to group windows, how many workers you need, which agents should use worktrees, or which agents need separate models or API routes, ask ccb_self. It is CCB's built-in self-agent: it understands CCB commands, config authority, roles, windows, reload behavior, and common recovery paths, and can design the config with its private ccb-config skill. Blank projects include ccb_self; existing custom configs can add it with ccb roles add agentroles.ccb_self:codex.
Validate the config:
ccb config validate
Start the workspace:
ccb
Type directly in an agent pane, or route work between agents:
/ask reviewer review the latest parser changes and list blocking issues.
Agents can also call /ask from workflow orchestration to delegate and hand off work automatically.
| Region | Purpose |
|---|---|
| Sidebar | Shows refresh/close CCB controls, windows and agents, internal communication state, and tips that can be edited in config and hot-reloaded. |
| Mouse control | Click to switch windows, agents, and panes; refresh, kill, or delete communication entries from the communication area. |
| Workspace | Every pane is a real CLI. Switch by mouse or tmux shortcuts. |
| Useful shortcuts | Ctrl-b h/j/k/l switches adjacent panes; Ctrl-b z zooms or restores the current CLI pane. |
Run ccb update rich to install the optional rich workbench; it bundles Yazi where possible, uses WezTerm for the rich terminal surface, and gives Markdown rendering plus image/PDF/video previews. After installation, plain ccb automatically opens this rich launcher unless it is already running inside a CCB-managed rich WezTerm; ccb rich remains available as an explicit launcher.
CCB supports the Agent Roles Spec, a host-neutral way to package specialist agents as portable Role Packs. The same repository also acts as the public role catalog.
| Role | Basic function |
|---|---|
agentroles.ccb_self |
CCB self-maintenance, config help, runtime diagnosis, guarded recovery, and workflow orchestration. |
agentroles.archi |
Architecture review, boundary checks, coupling analysis, maintainability risk, and practical next-step gates. |
agentroles.frontend_engineer |
Frontend design and implementation, design-system work, accessibility, browser QA, and reviewed AGY delegation. |
agentroles.mobile_app_engineer |
Mobile app design and implementation across iOS, Android, React Native, Expo, Flutter, SwiftUI, and Jetpack Compose. |
agentroles.mother |
Role creation, role-source audit, role research, blueprinting, and Agent Roles spec compliance review. |
agentroles.su_ccb |
SU-CCB workflow operation for requirement analysis, planning, dispatch, review gates, archive, and recovery. |
bfly123@126.comseemseam-comStart with Quick Start for first use. Open only the reference area you need.
| Topic | When to open it |
|---|---|
| Concepts and positioning | What CCB is, why multi-agent workflows help, and how CCB compares with other approaches. |
| Daily operation | Common commands and tmux basics for routine use. |
| Configuration and roles | .ccb/ccb.config, Role Packs, and ccb_self configuration help. |
| Collaboration and maintenance | Ask routes, install/update notes, FAQ, and credits. |
| Release notes | Current v7 highlights and historical release entries. |
CCB is a project-level agent CLI workspace. It uses tmux to manage multiple real CLI agents and unifies startup, restore, commu