Set Up Route

Part of Route. Start here to configure the product.

Choose Your Routes

Open Route. Until a machine syncs, the page opens on its Setup tab: six steps you can take in order or jump between. Once a machine or pick reaches your organization, Routes opens first and Setup moves to the last tab, where you can change providers and routes later. You start from our recommendations, which we update as models change.

1. Choose your providers. Pick Off, Plan, API key or Plan and API key for Claude Code, Codex and Antigravity. Muse Code supports Off or Plan. With both, Route uses the plan first and the API key when the plan has no room. Your keys stay on your machine; cedr.dev never asks for them.
2. Check the routes. Each route has a switch; turn off any you don’t want. The Routes tab has the same switches, and selecting a route there shows the models it tries, best first.
3. Save the routes. On Pro and up, owners and admins Save and sync so every machine picks them up. On any plan you can Download routes.toml and put it at ~/.config/cedr/routes.toml. Your choices carry from step to step but are not saved until you save.
4. Set up this machine. Hand the prompt to your agent, or follow the commands beside it: install the CLI, save your key, write routes.toml and sync.
5. Connect your agent. Hand over the prompt, or register the cedr MCP server yourself with the command for your agent.
6. Check it works. The step shows whether routes are saved, a machine has synced and the first pick has arrived.

The review council has its own page: open Council to choose its members (provider, plan or key, model and effort), how many reports are needed (the quorum), which findings block a change, and how many revision rounds a blocked change gets. Below the quorum the result is “incomplete”, never a pass. In a revision round the change’s author receives a single brief with every finding, fixes or rebuts each blocking one, and the council reviews it again. If it still blocks after the last round, the result stands.

Design and UI work always stay with your main agent.

Let Your Agent Do It

Each step that needs changes on your machine has a prompt you can hand to your own AI coding agent. Open it, check it, copy it and paste it into the agent’s chat:

• Set up this machine writes your routes (or the small machine file for saved routes) to ~/.config/cedr/routes.toml, checks with you which providers you have on that machine, connects Claude Code’s status line so Route can see your plan usage, and runs the first sync.
• Connect your agent registers Cedr with Claude Code or Codex and adds a short rule to the agent’s own instructions: pick a route before handing work to another model, and record how it went.
• Run the review council has every council member review your current changes, merges their findings and shows you the result.

The prompts never contain a key and tell the agent never to ask for one in the chat: when a step needs your cedr.dev key, the agent asks you to save it to a private file yourself.

Check This Machine

Install the CLI, then run:

cedr route list
cedr route pools

The first command should list the routes you enabled. The second should show a usable provider for the work you want to delegate. An unknown reading does not prove a plan has room: check the provider’s sign-in and usage reader before relying on it.

For Claude Code plan readings, set its user settings statusLine command to cedr route statusline. If a status line already exists, preserve it by wrapping its command and arguments with cedr route statusline --. Back up the settings before editing. Route cannot collect a Claude Code reading until a session supplies status-line input.

If you only want local routing, download the complete routes.toml with harnesses and routes, then omit [sync]. Do not use the small shared-routes machine file for local-only setup. No cedr.dev API key or MCP connection is required for local picks. To share activity later, follow Sync Routes Across Machines.

The Ask your agent menu at the top right of the Route page in the app has Tune my routes (suggests route and provider changes from your picks and verdicts) and Troubleshoot Route (runs cedr doctor and finds why picks fall back or never sync), beside Set up this machine and Connect my agent. Each copies a prompt filled in with your organization’s settings; see Ask Your Agent in the App.

Remove Route

Removing Route from a machine covers the routes.toml cedr uses, shared routes pulled by cedr route sync, the ## Cedr Route section in your agents’ instruction files, the cedr MCP server and Claude Code’s status line. Council and Monitor use some of these, so keep what they need. The CLI stays, and picks already synced stay in the app. In the app, Ask your agent has Remove Route from this machine; this is the same prompt without your organization’s details:

Remove Cedr Route from this machine.

Before deleting anything, list every file, setting, registration and scheduled job you would remove, with its path, and wait for my approval on each one. Skip anything I want to keep. Back up every configuration file you will change or delete into a new folder ~/cedr-backup-<YYYY-MM-DD>/ first, keeping its path. Never touch my organization's data in the cedr.dev app. Finish by telling me what you removed, where the backups are and what is left.

1. Find what Route set up here and list it: the routes.toml cedr uses ($CEDR_ROUTES, .cedr/routes.toml in this repo, or ~/.config/cedr/routes.toml), shared routes pulled by cedr route sync under ~/.config/cedr/org-routes/, the ## Cedr Route section in my agents' instruction files (~/.claude/CLAUDE.md, ~/.codex/AGENTS.md), the cedr MCP server registration, and Claude Code's status line in ~/.claude/settings.json.

2. Council reads routes.toml and the cedr MCP server too, and Monitor reads Claude Code plan usage through the same status line. Ask me whether I still use Council or Monitor; keep what they need.

3. Remove what I approve. For the status line: if it is exactly cedr route statusline, remove the statusLine setting; if it wraps another command (cedr route statusline -- <command>), put back just that command. Remove the MCP server with the agent's own command (for example claude mcp remove cedr or codex mcp remove cedr), or by deleting its entry from the agent's MCP config.

4. Offer to delete Route's local history and readings too: ~/.local/state/cedr/route-history.jsonl, ~/.local/state/cedr/readings/ and ~/.cache/cedr/readings-*.json. Back them up first.

5. Keep the cedr CLI; other products may use it. Finally run cedr doctor and show me what it reports.

By hand: back up, then delete ~/.config/cedr/routes.toml (or the file $CEDR_ROUTES names) and ~/.config/cedr/org-routes/; remove the ## Cedr Route section from ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md; run claude mcp remove cedr or codex mcp remove cedr; and in ~/.claude/settings.json remove a statusLine of exactly cedr route statusline, or put back the command it wraps. Optionally delete ~/.local/state/cedr/route-history.jsonl, ~/.local/state/cedr/readings/ and ~/.cache/cedr/readings-*.json.

Continue with Picks and Verdicts.