Picks and Verdicts

Part of Route.

Before You Start

Complete Set Up Route. Route selects a model; your coding agent or orchestrator starts the work and checks its result.

Pick, Run and Check

A pick is the start of the work, not its result

1. PickDelegated pick: continue with the model, effort and pick ID. keep: the main agent does and checks the work; stop this flow.
2. →RunYour agent starts the selected worker
3. →CheckReview its result and run acceptance checks
4. →RecordSave a verdict against the pick ID

Run, Check and Record apply only to delegated picks. A keep result has no delegate, pick ID or history record. Route does not execute the selected worker.

cedr route pick review.code --size medium

Use a route name from cedr route list. Read the returned tag, model, effort and pick ID. Start the delegated brief with the tag, describe the exact task and its acceptance checks, then run the selected model through your agent’s supported delegation mechanism.

A successful pick exits with 0. A keep: result exits with 1 and means your main agent should handle the task itself. Exit 2 means a configuration, usage or I/O error; resolve that error before retrying. Never invent an available model when a provider is missing.

When you explicitly want one model, cedr route manual <provider>/<model> creates its tag and pick record without routing. Use --avoid <provider> on a normal pick when that provider cannot take the task.

Record the Outcome

Read the result and run the checks appropriate to the task, then use the actual pick ID:

cedr route verdict p-979e77351990 accepted

Verdict	Use it when
accepted	You used the result as delivered.
reworked	You used it after making corrections.
redone	You or another agent had to redo the work.
rejected	You did not use the result.

An agent finishing successfully is not by itself evidence that its work was accepted. Record the verdict after verification. Keep any verdict note free of prompts, code, credentials and private task details.

Inspect Local History

cedr route history --limit 20
cedr route stats --route review.code
cedr route pick review.code --size small --format json

JSON output is for scripts and agents; the example pick still records a real pick. Use --no-record if you only want to inspect a proposed pick. Local history and the app’s retained history are separate; activity and history explains what is shared.

A pick that names a judge or escalation route needs the additional steps in Drafts, Judges and Model Versions.