Cardea

One subscription, login, or key can run out. Different models are also good at different work. Cardea gives you one CLI, local dashboard, and MCP server that can route tasks across Claude Code, Codex, Grok, and any OpenAI-compatible endpoint by cost and strength.

Measured results and practical routing rules live in docs/ROUTING.md. In our own use, moving implementation to workers and reviewing in a fresh context cut coordinator-side cost by an estimated 85% — one project, so read the caveats.

Bring your own keys, or load Cardea into the LLM you already use.

Quick Start

Install the latest release (Node 20.10+, no npm account or registry needed):

npm install -g https://github.com/SeaHorseCapn/cardea/releases/latest/download/cardea-cli.tgz
cardea doctor

Or from a clone, if you want to hack on it:

git clone https://github.com/SeaHorseCapn/cardea.git
cd cardea
npm install
npm run build
npm link

Install the vendor CLIs you want Cardea to use, then log in to each one once:

claude
codex
grok
cardea doctor

By default, Cardea uses those CLI logins for claude, codex, grok, and the coordinator. It scrubs each worker's API-key environment variable from the child process, so a stray exported key will not override the vendor CLI login. Cardea requires Node >=20.10.

Related MCP server: codex-worker-runtime

Three Ways To Use It

CLI

cardea "Review this repository for release blockers"
cardea "Check this implementation with a second opinion" --model codex
cardea "Compare approaches for this API" --panel --tier fast
cardea doctor --live

Useful flags:

Dashboard

cardea serve

Open http://127.0.0.1:4317. The dashboard is not authenticated; bind it only to localhost or a private network you control.

MCP Inside Your LLM

Claude Code:

claude mcp add cardea -- cardea mcp

Codex CLI config.toml:

[mcp_servers.cardea]
command = "cardea"
args = ["mcp"]

Generic MCP JSON:

{
  "mcpServers": {
    "cardea": {
      "command": "cardea",
      "args": ["mcp"]
    }
  }
}

The MCP tools are list_workers, delegate, fan_out, and panel. panel returns separate answers; the host LLM synthesizes them. Start with cardea mcp --allow-writes if you want MCP delegate calls to be allowed to request writes.

Using API Keys Instead

API keys are opt-in. Configure one worker explicitly:

{
  "workers": {
    "codex": {
      "auth": "api-key"
    }
  }
}

Then export the matching key in the same shell that starts Cardea:

export OPENAI_API_KEY=...
cardea doctor

To opt all default CLI workers and the coordinator into API-key auth:

{
  "coordinator": {
    "auth": "api-key"
  },
  "workers": {
    "claude": { "auth": "api-key" },
    "codex": { "auth": "api-key" },
    "grok": { "auth": "api-key" }
  }
}

Each CLI worker supports:

• auth: "cli-login": default; scrub that worker's key env var and use the account logged into the vendor CLI.

• auth: "api-key": require the key env var and fail fast if it is missing.

• auth: "auto": pass the key through when its env var is set, otherwise use the vendor CLI login.

Coordinator auth uses the same modes under coordinator.auth; its default is also cli-login. API-key auth may be useful for automation. See ACCESS.md.

Cardea never reads keys from config and never stores key values.

Workers And Tiers

Defaults are configurable in ~/.cardea/config.json.

OpenAI-compatible workers are text-only: no tools and no file access.

OpenAI-Compatible Workers

Define as many named endpoint workers as you need:

{
  "workers": {
    "openrouter": {
      "kind": "openai-compatible",
      "enabled": true,
      "baseUrl": "https://openrouter.ai/api/v1",
      "apiKeyEnv": "OPENROUTER_API_KEY",
      "tiers": {
        "fast": { "model": "openai/gpt-4o-mini" },
        "standard": { "model": "anthropic/claude-sonnet-4.5" },
        "deep": { "model": "openai/gpt-5" }
      }
    },
    "ollama": {
      "kind": "openai-compatible",
      "enabled": true,
      "baseUrl": "http://127.0.0.1:11434/v1",
      "auth": "auto",
      "tiers": {
        "fast": { "model": "llama3.2:3b" },
        "standard": { "model": "qwen2.5-coder:14b" },
        "deep": { "model": "qwen2.5:32b" }
      }
    }
  }
}

Then run cardea "summarize these notes" --model openrouter --tier fast.

Fan Out Pattern

Use a cheap wide pass, then escalate only the interesting results:

cardea "Use fan_out fast over the changed files, identify only the risky ones, then ask a deep worker to verify those findings."

The coordinator also has a fan_out tool. It runs one template over up to 20 items in parallel.

Safety

Runs are persisted to ~/.cardea/runs/*.jsonl. safety.protectedPaths defaults to []; add paths that should always stay read-only:

{
  "safety": {
    "protectedPaths": ["/path/to/critical/repo"]
  }
}

--allow-writes lets workers write only when requested and never under protected paths. MCP has a second gate: writes are refused unless the server was started with cardea mcp --allow-writes.

Troubleshooting

Run:

cardea doctor
cardea doctor --live

Vendor model IDs change. Override them per tier:

{
  "workers": {
    "grok": {
      "tiers": {
        "fast": { "model": "grok-4.6" },
        "standard": { "model": "grok-4.6" },
        "deep": { "model": "grok-4.5" }
      }
    }
  }
}

If an API-key worker fails, confirm the named env var is exported in the same shell that starts Cardea. If a CLI-login worker fails, sign into that vendor CLI interactively and rerun cardea doctor --live.

Architecture

src/core never imports from src/cli or src/server; the contract is RunOptions in, a JSON-serializable CardeaEvent stream out. The CLI, dashboard, and MCP server use the same core worker adapters and event stream.