Codex CLI
OpenAIOpenAI's open-source coding agent that runs locally in your terminal. In CodeBee it acts as the planning hub, turning goals into executable step lists.
SUPPORTED CLIS
The 14 AI CLIs CodeBee supports
No single-model lock-in. Any supported AI coding CLI already on your machine can join the hive and take a role; every CLI you add is another way to work.
Which AI coding CLIs does CodeBee support?
CodeBee currently orchestrates 14 local CLIs across four roles: planning — Codex CLI, Roo Code; execution — Claude Code, Qwen Code, OpenCode, Aider, Cline, Goose, Amazon Q CLI; research — Gemini CLI, Kimi Code; review — GitHub Copilot CLI, Cursor Agent, Windsurf. CLIs are discovered automatically and the list keeps growing.
The list and per-release changes are documented in the GitHub repository (Vercel-By-WXP/CodeBee) release notes.
- Count
- 14 local CLIs covering 4 task roles
- Onboarding
- Installed CLIs are discovered automatically — no per-tool wiring
- Roles
- Plan · Build · Research · Review
- Model vendors
- OpenAI, Anthropic, Google, Alibaba Qwen, Moonshot AI and more — accounts and keys stay yours
- Install all?
- No. One CLI is enough to run; more CLIs mean richer routing and cross-review
PLAN
Planners
Break down the goal, arrange the steps, decide who takes the next round.
Planning hub
Roo Code
Open sourceAn open-source AI coding assistant. In CodeBee it excels at splitting big tasks into small steps that set up the builder swarm.
BUILD
Builders
Hands on the work: write code, edit files, run commands, turn plans into artifacts.
Claude Code
AnthropicAnthropic's agentic coding tool — reads your codebase, edits files and runs commands. In CodeBee it carries the deep execution work.
Qwen Code
Alibaba QwenA command-line coding assistant built on Qwen models. In CodeBee it handles fast implementation and parallel changes.
OpenCode
Open sourceAn open-source terminal coding assistant that supports many models. In CodeBee it serves as the open-model builder seat.
Aider
Open sourceThe classic AI pair-programming tool. In CodeBee it handles incremental edits and pairing in the terminal.
Cline
Open sourceAn open-source autonomous coding agent. In CodeBee it takes on multi-step agentic execution.
Goose
BlockBlock's open-source automation agent. In CodeBee it runs routine tasks automatically.
Amazon Q CLI
AWSAWS's command-line AI coding assistant. In CodeBee it covers cloud engineering and infrastructure tasks.
RESEARCH
Researchers
Search sources, read long documents, scout in parallel, feed context to the team.
Gemini CLI
GoogleGoogle's open-source command-line agent. In CodeBee it runs parallel exploration and source retrieval.
Kimi Code
Moonshot AIMoonshot AI's assistant, strong with long context. In CodeBee it reads and organizes long documents and sessions.
REVIEW
Reviewers
A second pair of eyes: score by dimension and only pass work that meets the bar.
GitHub Copilot CLI
GitHubGitHub's official CLI coding assistant. In CodeBee it joins reviews from the completion-and-suggestion angle.
Cursor Agent
AnysphereCursor's agent mode. In CodeBee it serves as a code reviewer checking change quality.
Windsurf
WindsurfThe Windsurf agentic IDE. In CodeBee it cross-validates across models as the second pair of eyes.
HOW IT CONNECTS
Install once,
discovered automatically.
CodeBee automatically discovers supported CLIs installed on your machine: confirm them in the "Local agent catalog", set default models, and leave the routing to the hive. Each CLI's account, keys and billing stay with its own vendor.
01
Install any one CLI
Install and sign in following the vendor's docs — say Codex CLI, Claude Code or Gemini CLI.
02
Confirm in the agent catalog
Open CodeBee's "Local agent catalog" and confirm the new CLI was discovered and enabled.
03
Set the default model
Configure default models under "Model providers", or let CodeBee route by role automatically.
CLI FAQ
Supported CLIs, answered.
The list, onboarding, billing boundaries and how to request more — direct answers.
Which AI coding tools does CodeBee support?
CodeBee currently orchestrates 14 local CLIs:
- Planning: Codex CLI, Roo Code
- Execution: Claude Code, Qwen Code, OpenCode, Aider, Cline, Goose, Amazon Q CLI
- Research: Gemini CLI, Kimi Code
- Review: GitHub Copilot CLI, Cursor Agent, Windsurf
The list keeps growing with each release — see the GitHub release notes.
Do I have to install all 14 CLIs?
No. One CLI is enough to start: a single CLI can still run the full plan → execute → verify → review loop. The more CLIs you install, the more room there is for role routing and cross-model review. A good minimum is one builder (say Claude Code or Qwen Code) plus a reviewer from a different vendor, so the second pair of eyes comes from a different model family.
Who manages the accounts, keys and billing for these CLIs?
Each CLI is a product of its own vendor: account signup, API keys, quotas and billing are all managed by that vendor. CodeBee only orchestrates the calls on your machine — it never touches or stores your keys or request content. Which vendors to use and how to configure them is entirely your call.
How can I ask for a new CLI to be supported?
Open an issue in the GitHub repository with the CLI's name, install method and official link. The list keeps growing with each release.
RECOMMENDED COMBOS
Pair them by scenario
for the best results.
Common pairings based on the four roles. One CLI is enough to run; these combos simply leave more room for cross-review — every CLI is interchangeable, and what you have installed is what counts.
| Scenario | Builder | Plan / research | Review |
|---|---|---|---|
| Everyday development | Claude Code | Codex CLI | Cursor Agent |
| Long-document research | Kimi Code | Gemini CLI | Windsurf |
| Rapid prototyping | Qwen Code | Roo Code | GitHub Copilot CLI |
| Routine automation | Goose | Codex CLI | Windsurf |
| Cloud engineering | Amazon Q CLI | Codex CLI | Cursor Agent |
These are pairing suggestions, not configuration requirements: CodeBee routes across the CLIs you have installed and never calls anything outside the list.