Install the CLI

The cedr command line tool makes every Route pick and Council merge on your own machine, compiles your agents’ setup with Sync, reads their usage for Monitor, and runs Guard’s checks on your repos. It is free and open source, and it never reads your agents’ credentials.

Prefer agent-assisted setup? Start with Set Up cedr With an Agent. It asks which products and MCP connection you want before installing or configuring anything.

Install

Download the archive for your platform from the latest release, unpack it and put cedr on your PATH.

Platform	Archive
Linux x86_64	cedr-linux-x86_64.tar.gz
Linux ARM64	cedr-linux-arm64.tar.gz
macOS, Apple silicon	cedr-macos-arm64.tar.gz
macOS, Intel	cedr-macos-x86_64.tar.gz
Windows x86_64	cedr-windows-x86_64.zip

For example, on Linux x86_64:

curl -fsSL https://github.com/Sheernox/cedr/releases/latest/download/cedr-linux-x86_64.tar.gz | tar -xz
install -m 755 cedr-linux-x86_64/cedr ~/.local/bin/cedr
cedr --version

Linux builds need glibc 2.34 or newer (Ubuntu 22.04, Debian 12, RHEL 9 or later). Every release lists SHA-256 checksums in SHA256SUMS, and carries signed build provenance you can check with gh attestation verify <archive> --repo Sheernox/cedr.

To build from source instead, use a current stable Rust toolchain:

cargo install --locked --git https://github.com/Sheernox/cedr cedr

Upgrade

From 0.5.0 on, cedr keeps itself up to date: once a day it checks for a new release in the background, checks the download against the release’s SHA-256 checksums, and replaces itself. The next command tells you it did. To update right away, or to see whether you are on the latest release:

cedr update           # install the latest release
cedr update --check   # only report
cedr update --auto off

cedr update --auto off (or CEDR_NO_AUTO_UPDATE=1) turns the daily update off, and cedr update --version 0.5.0 installs a particular release, older ones included. cedr never updates itself in CI. If you installed with cargo install, or into a directory you cannot write to, it tells you how to update instead. Your routes, history and locks stay where they are. The changelog lists what changed and any step a release needs.

On a release before 0.5.0, download the new release the same way as above and replace the old cedr once.

Upgrading to 0.3.0 from an earlier release? Run cedr lock once in each repo you have locked with Guard. It moves cedr.lock into .cedr/guard.lock; commit the change.

Release 0.4.0 adds cedr sync, cedr monitor and cedr doctor; nothing changes for existing routes, history or locks.

Usage Data

cedr sends anonymous usage data (which commands run, how they end, your OS and which coding agents are installed) to help us improve it. It never sends arguments, paths, repo names or code. Usage Data lists every field and how to turn it off: cedr telemetry off.

Check Your Setup

cedr doctor checks everything cedr needs on this machine and in the current repo: the CLI version, your API key and organization, Route’s config and readers, the MCP registrations, Monitor’s collectors and schedule, and Sync and Guard in the repo. Each problem comes with the command that fixes it. cedr doctor --format json gives the same to your agent.

Turn On Shell Completion

cedr completions <shell> prints a completion script for bash, zsh, fish, PowerShell or Elvish:

cedr completions bash > ~/.local/share/bash-completion/completions/cedr   # bash
cedr completions zsh > ~/.zfunc/_cedr                                     # zsh, with ~/.zfunc on fpath
cedr completions fish > ~/.config/fish/completions/cedr.fish              # fish
cedr completions powershell >> $PROFILE                                   # PowerShell
cedr completions elvish > ~/.config/elvish/lib/cedr.elv                    # Elvish, then use cedr in rc.elv

Open a new shell to pick it up.

Make Your First Pick

1. Get a routes.toml. Open Route in the app, choose your providers, and download the file to ~/.config/cedr/routes.toml. Route explains each setting.

2. Pick. Ask which agent should take a kind of work:

   cedr route pick review.code

   The first line is the route tag: the route, the chosen model and effort, why it won, and the pick’s ID.

3. Record how it went. When the work is done, record a verdict on that pick: accepted, reworked, redone or rejected.

   cedr route verdict p-979e77351990 accepted

   cedr route stats then shows which model does each kind of work best.

Sync With the App

Sync sends your picks, verdicts and council results to your organization, so the app can show them, and fetches routes you saved there.

1. Add your organization to routes.toml:

   [sync]
   org = "org-1a2b3c4d5e6f"   # your organization ID, shown in the app

2. Create a key on the API keys page. Put it in the CEDR_API_KEY environment variable, or save it to ~/.config/cedr/api-key and make that file private with chmod 600.

3. Run the first sync:

   cedr route sync

After that, cedr syncs in the background as you work.

Next Steps

• Review risky changes with several vendors in Council.
• Keep every agent’s rules, skills and MCP servers in step with Sync.
• See every agent’s usage, spend and plan limits with Monitor.
• Pin the skills and MCP servers your agents load with Guard.
• Connect your agent to the CLI’s tools with Local MCP.