cc-suite plugin
A plugin that syncs Claude Code, Codex CLI and Antigravity on one project and lets them hand work to each other.
- 57 ★ on the repository
- Last commit
- ISC
Broad access
Why this level
- The plugin runs other agent CLIs that read and change project files.
- The bridge to Codex can expose Claude session history to it, so conversation content goes to another vendor.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/cc-suiteDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The plugin runs other agent CLIs that read and change project files.
- The bridge to Codex can expose Claude session history to it, so conversation content goes to another vendor.
This is third-party code. Review the repository files before installing.
What it does
cc-suite fixes the problem of agents reading different files: each has its own instructions, skills and hooks. The plugin makes `AGENTS.md` the single source of instructions and turns `CLAUDE.md` into a thin import. The `.agents/skills/` folder becomes a link to `.claude/skills/`, hooks are mirrored into `.codex/hooks.json` and servers from `.mcp.json` land in the Codex and `agy` configuration. On top sit work-handoff commands. From Claude Code, `/cc-suite:audit`, `/cc-suite:implement` and `/cc-suite:bug-analyze` run through `codex exec`, with Grok Build delegation over ACP and a bounded code review in Qwen Code. In reverse, the claude-octopus MCP server gives Codex the `$claude-review`, `$claude-plan`, `$claude-implement` and `$claude-debug` skills. Jobs are tracked, can run in the background and respect deadlines.
Who it is for. Developers who keep Claude Code and Codex in one repository and do not want to duplicate instructions, hooks and MCP settings.
Good fit when
- Skills written for Claude must also work for Codex without copying folders.
- You want Codex to give an independent review of changes prepared in Claude Code.
- Hooks are kept in two places and drift apart.
- You need a quick code review by an outside agent in a sandbox, for example Qwen Code.
Not a fit when
- The project has one agent and shared files serve only that agent.
- Another agent must not read Claude session history: conversation content would go to a different vendor.
- Codex, Antigravity, Grok Build or Qwen Code is not installed: each handoff lane needs its own binary.
Example request
Run `/cc-suite:init`, pick Codex and Antigravity, then hand the latest changes to Codex for review with `/cc-suite:audit`.Limitations
Each handoff lane needs its agent installed: Codex CLI, Antigravity CLI, Grok Build or Qwen Code 0.21.0 or newer. The Codex to Claude path goes through `claude-octopus`, fetched at run time with `npx -y` and sharing the credential store of the Claude CLI. Reading Claude history from Codex exposes conversation content, that is, sends it to OpenAI. The session list is limited to the repository by default, and `all_projects: true` widens it to every project on the machine.
How to disable. Remove the plugin with `claude plugin uninstall` and delete the created `.codex/` files and the `.agents/skills` link by hand. For Codex and `agy` remove the registered `claude-code` server.
FAQ
How do I install cc-suite?
Through the community marketplace: `claude plugin marketplace add anthropics/claude-plugins-community`, then `claude plugin install cc-suite@claude-community --scope project`. Newer versions appear first in the xiaolai marketplace: `claude plugin marketplace add xiaolai/claude-plugin-marketplace`.
Where do I start after installing?
Run `/cc-suite:init`. It probes `PATH`, lists the agents you have and writes configuration only for the selected ones, so a Claude-only project gets no `.codex/` tree.
How do I hand a task to Codex?
Use `/cc-suite:audit`, `/cc-suite:implement` or `/cc-suite:bug-analyze`. Check a job with `/cc-suite:status`, read the result with `/cc-suite:result` and cancel with `/cc-suite:cancel`.
How does Codex reach Claude?
Through the `claude-code` MCP server (claude-octopus) registered in `.codex/config.toml`. Codex gains the `$claude-review`, `$claude-plan`, `$claude-implement` and `$claude-debug` skills.
Which other agents can be connected?
Grok Build, opencode, Qwen Code and Kimi CLI. Pick them in the `Enabled Tools` list of `.cc-suite.md`, and `/cc-suite:bridge-tools` mirrors the project MCP servers to them.
Discussion
No questions or reviews yet.
Related
PluginsMulti-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
One config for Claude Code and Codex in every repo: shared rules, skill packs, second-model review and a destructive-command guard
A Claude Code skill that hands implementation-heavy work to Codex CLI while Claude keeps planning, review and acceptance.
A Claude Code plugin that hands coding tasks to Codex agents, monitors them and verifies the results independently
Three Claude Code commands that bring Codex in for a second opinion on a plan, a plan critique and brainstorming in read-only mode
Claude Code supervises while Codex, opencode and pi work on your quota: delegated edits, independent review, model discussions
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| cc-suite (this card) | no | 57 | |
| Claude Octopus | no | 4,437 | orchestrates several models from Claude Code; cc-suite syncs agent files and hands tasks off both ways |
| Harness for Codex | no | 68 | a plugin that assembles a subagent team inside Codex; cc-suite links Claude Code, Codex and Antigravity in one project |
README in short
The README explains why agents keep different settings files and condenses the plugin features into a table. Installation, prerequisites, a command list and notes on privacy and the limits of each handoff lane follow.