by bfly123
Real-time multi-AI collaboration: Claude, Codex & Gemini with persistent context, minimal token overhead
# Add to your Claude Code skills
git clone https://github.com/bfly123/claude_code_bridgeGuides for using ai agents skills like claude_code_bridge.
Last scanned: 4/24/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-24T06:08:23.878Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}No comments yet. Be the first to share your thoughts!
Native multi-agent runtime for terminal split panes Claude · Codex · Gemini · OpenCode · Droid Visible concurrency, native communication, project-scoped runtime
English | Chinese

Introduction: CCB v6 is the infinite parallel agents edition. It turns split-pane collaboration into a native multi-agent runtime where agents can run side by side, hold independent roles and personalities, and delegate to each other through a stable built-in communication layer.
Parallel agents are not just "more panes on screen". In CCB, each agent can own a fully independent role, task stream, skill library, and personality.
CCB provides the runtime foundation for stable agent-to-agent communication and effectively unbounded delegation. It supports arbitrary agent naming and window arrangement, per-agent control, broadcast dispatch, and point-to-point communication.
ccb start, restore, and attach CCB in the project directory from the terminalccb -s safe modeccb -n rebuild the project .ccb stateccb kill close CCBccb kill -f deep-clean exitInside a provider / agent runtime:
/ask all "sync on the latest repo state" broadcasts one message to all live agents./ask reviewer "review the new parser change" sends work to the named [reviewer] agent.Typical pattern:
ask all for one-shot broadcast or global syncask agent_name for targeted delegationask themselves, and skills are currently auto-installed into Codex, Claude, and other providerspend and watch are secondary toolsccb is controlled by .ccb/ccb.config. That file defines agent names, pane layout, and whether an agent runs inplace or in a separate git worktree.
Quick rules:
agent_name:provider defines one agent. agent_name is also the pane label and logical runtime name.cmd adds one shell pane.; splits panes horizontally from left to right., splits panes vertically from top to bottom.inplace. If one agent needs an isolated git worktree to avoid conflicts, write agent_name:provider(worktree).Example:
cmd; writer:codex, reviewer:claude; qa:gemini(worktree)
This layout means:
cmdwriterreviewer and qaqa runs in an isolated git worktree; writer and reviewer run inplace in the main projectHistorical note: older release notes below may mention askd, legacy flags, or removed commands. Those references are kept only as changelog history and do not redefine the current CLI surface.
.tmp/plugins/ and .tmp/plugins.sha, so isolated agents inherit the marketplace catalog and installed plugin assets they actually need instead of starting with plugin-enabled config but missing bundlescmd pane now directly execs the resolved user shell and preserves ordinary user-session transport variables such as DISPLAY, WAYLAND_DISPLAY, DBUS_SESSION_BUS_ADDRESS, XAUTHORITY, and SSH_AUTH_SOCK, improving fish/zsh and GUI-command compatibilityconfig.toml and auth.json as the sole authority for explicit key / url routes, so agent-scoped API overrides replace inherited global provider routes instead of drifting back to system configsessions/ namespaces before launch when the bound route no longer matchesccb startup now seeds tmux namespace creation from the real terminal viewport and issues a best-effort client refresh after attach so first paint matches the current terminal size without manual redrawccb update.ccb/ccb.config now accepts flat per-agent key, url, and model shortcuts so common provider overrides stay concisedist-macos-smokeccb start now reads install-scoped cached release metadata and only prompts when a newer stable release is already known locallyno server running on <project socket> as an absent namespace that must be created, instead of failing startup as a generic tmux inspect errorccb -> ping -> kill blackbox lifecycle stays coveredno server running as a recreate signal rather than a fatal inspect failureoauth_creds.json for oauth-personal reuse, and remove stale copied credentials when auth inheritance is disabledrespawn-pane now uses the same tmux ready-retry budget as namespace create/reflow, reducing transient no server running failures during startup and supervisionoauth_creds.json alongside other provider credential artifacts