Route

Route picks the coding agent, model and effort for each kind of work, such as a code review or deep research. Within each step it sends the work to the plan with the most room left and skips plans near their limits, so every plan you pay for gets used. The cedr command line tool makes each pick on your machine; the Route page in the app is where you choose your routes and see how they perform.

Choose Your Routes

Open Route. You start from our recommendations, which we update as models change.

1. Your providers. Under Setup, choose Off, Plan, API key or Both for Claude Code, Codex, Antigravity and Muse Code. 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. Routes. The routes table has a switch for each route; turn off any you don’t want. Open a route to see the models it tries, best first.
3. Review council. Open Council to choose the council’s 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.
4. Use it. Under Setup (or Settings on the Council page), download routes.toml and put it at ~/.config/cedr/routes.toml, or, on Pro and up, save your routes so every machine picks them up.

Design and UI work always stay with your main agent.

Drafts, Judges and New Models

Some routes draft cheaply first. Bulk edits, implementation and source gathering hand their result to the Draft judge route, a fast model that reads the draft against its brief and checks and either accepts it or escalates it: bulk edits escalate to implementation, implementation to hard problems, and source gathering to deep research. Turn off the route a cascade escalates to and your main agent takes escalated work itself; turn off the Draft judge and those routes run without one. Your agent records a verdict on the judge’s call as well, so you can see in the routes table how many drafts each judge escalated, and whether it is earning its place.

Routes name model families, and each pick uses the newest version your provider offers that we have evaluated. A newer version that has not been evaluated yet is a preview: small tasks try it, so it builds a track record, while medium and large work stays on the evaluated version. Once a preview version’s verdicts hold up, the next recommendations update promotes it. In a routes.toml you edit yourself, [evaluation] preview sets this: trial (the default) as described, hold to keep previews off every pick, or use to take the newest version at once. Picks on a preview version are marked (preview) in their tag.

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.

Keep Machines in Step

On Pro and up, owners and admins can Save and sync. Saved routes follow our recommendations as they change, without saving again. On each machine:

1. Create a key on the API Keys page.
2. Put the small machine file from Preview the files at ~/.config/cedr/routes.toml. It names your organization and how that machine reads its plan usage.
3. Run cedr route sync with the key in CEDR_API_KEY.

Each sync pulls the saved routes and sends the machine’s picks, verdicts and plan state. Once a machine is set up, it also syncs on its own in the background, at most every 10 minutes while you work. Run cedr route sync yourself to see the result, including any error from a background sync.

Saved routes assume everyone in the organization has the same plans, and each machine checks that for itself:

• A provider whose program isn’t installed on the machine is never picked there. To leave out a provider you have installed but don’t use, add it to the machine’s own file:

  [machine]
  skip = ["antigravity"]

• If your routes add a provider after a machine was set up, that machine can’t read the new plan’s usage yet. cedr warns about it, and the Machines table on the Route page flags it. Run Set up this machine on it again.

Activity

Route opens with the totals for the period: picks, the share accepted, the median time from a pick to its verdict, how many judged drafts were escalated, and any model version on trial. The routes table then shows each route’s picks, accepted share, median time and cascade outcomes. Open a route to see each step’s models with how often their work was accepted, based on the verdicts members record; fewer than 10 verdicts is marked provisional, and a version on trial has its own line. Below are results by task size, your machines and recent picks. Filter by member or period at the top.

Council shows how the review council did: merges, passes, changes sent back for revision and how many of those then passed, each member’s reviews and findings, and recent results with the findings each found at each severity. Only counts reach cedr.dev, never the findings themselves.

Choose a machine under Plan state from to see each plan’s state on it (ready, conserving, out, unknown, or not on this machine) and which model it would pick next for each route. The Machines table lists each machine that synced in the last 30 days, whether it has the latest saved routes, and any provider or usage reader it is missing. Owners and admins see every member’s machines; members see their own.

Only routing details are synced: routes, models, reasons, verdicts, each plan’s state and the machine’s name (its host name unless you set name under [machine]), never prompts, briefs or code.

Plan	Activity kept	Saved routes
Free	30 days, up to 50,000 picks	Download only
Pro	1 year, up to 250,000 picks	Yes
Team	1 year, up to 1,000,000 picks	Yes, for every member
Business	3 years, up to 5,000,000 picks	Yes, for every member

Activity keeps the newest picks when either limit is reached. Your local history stays on your machine.

Connect an Agent to Hosted MCP

Open MCP in the app and copy a setup prompt into your agent’s chat. It connects to the hosted server with browser sign-in or a personal API key and verifies a read call for your selected organization.

Hosted MCP provides routes, synced activity, machine snapshots and Council tools on every plan. It does not replace the local connection that makes live routing picks. See Hosted MCP for setup, tool details, permissions, limits, monitoring and troubleshooting.