Sync Routes Across Machines

Part of Route.

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 tab on the Route page flags it. Run Set up this machine (step 4 of Setup) on it again.

Choose What to Share

Route synchronization is separate from the Sync product, which generates repository agent configuration. It is also separate from connecting Hosted MCP.

The key can be supplied through CEDR_API_KEY or the private file ~/.config/cedr/api-key (mode 600). Never put a key in routes.toml. Use a key with write access for uploads; see Authentication.

For a machine that keeps its own routes while uploading activity, use:

[sync]
org = "org-1a2b3c4d5e6f"
routes = "local"

For shared organization routes, use the machine file from the app. Run cedr route sync explicitly to see connection failures. Check membership, key expiry and the selected organization when a sync fails. A saved route configuration does not install providers or grant access to their paid plans.

To stop automatic Route synchronization while keeping shared routes available, set auto = false under [sync]. Manual cedr route sync still works. Do not remove [sync] from a shared-routes machine file: that file relies on the downloaded organization configuration for its harnesses and routes. For fully local routing, first replace it with a complete downloaded routes.toml, then omit [sync]. This does not delete previously uploaded activity or stop Monitor’s separately configured uploads.