Skip to content

Screens / Talking to the agent

Plan review

Show what the agent is about to do as steps a person can trim, question and accept before anything runs.

For: The person who asked for the work, and sometimes a second reviewer.

Markdown

3 ways to lay it out

1. Inline card in the thread

Pick it when: Short plans in a conversation: a handful of steps the person can read at a glance.

A thread with a plan card of three steps on a rail and Ask for changes and Accept buttons.
  • PlanProSteps to trim and accept, then the live run; sent back, it shows what was proposed, marked as not accepted.
  • Clarifying questionsProWhat the agent needs to know first; the recommended answer is marked, never pre-selected.
  • Step listFreeOrdered steps on a rail that fills as they finish.
  • Comment threadProA question about one step, between people and the agent, anchored to it; it says when the step has changed since, as your app reports it.
Install inline card in the thread

Pro and Premium items need a licence key; free ones install as they are.

2. Plan beside the evidence

Pick it when: Plans that change real things: reviewers need each step's log, diff and reach next to it.

The plan down the left; the selected step's log, diff and blast radius on the right.
  • Review canvasProThe plan on one side; a selected step's log, diff, blast radius and reasoning on the other.
  • Blast radiusProWhat a step can reach.
  • Change diffProThe change as files, one tab per file.
  • Review ladderProHow much is reviewed before agents act: from Advise to Full delegation.
Install plan beside the evidence

Pro and Premium items need a licence key; free ones install as they are.

3. Last look before shipping

Pick it when: The plan has run and the change is about to reach production.

A full page with the change, a checklist of checks and one Ship button.
  • Ship reviewProWhat ships, each check it must pass, and who signed off.
  • Test resultsProA test run that leads with what failed.
  • Approval requestProA second person approves the exact change, tied to it by a hash.
Install last look before shipping

Pro and Premium items need a licence key; free ones install as they are.

Rules that matter most here

Already covered elsewhere

Brief for a coding agent

Paste this into the agent that builds the screen. The docs MCP server returns the same text from get_screen.

Build a plan review with Candor UI: before the agent acts, show its plan as steps in a Plan the person can trim and accept.
Ask first with ClarifyingQuestions; mark the recommended answer but never pre-select it.
Proposed, the person drops steps they don't want and accepts or asks for changes; accepted, the same Plan becomes the live run with each step's status; sent back, it shows what was proposed, marked as not accepted.
For plans that change real things use ReviewCanvas: the plan on one side, the selected step's log, diff (ChangeDiff), BlastRadius and reasoning on the other.
Pass steps as plain data (id, title, status); Candor does not run the plan, your server does.
The agent's reasoning is shown as its own account. If a step's reach couldn't be measured, say so instead of showing an empty list.
Link to the agent-plan-ui pattern for the full flow.

Start from the "Inline card in the thread" layout: A thread with a plan card of three steps on a rail and Ask for changes and Accept buttons.
Candor items: plan (https://candor.themethodic.com/docs/plan.md), clarifying-questions (https://candor.themethodic.com/docs/clarifying-questions.md), step-list (https://candor.themethodic.com/docs/step-list.md), comment-thread (https://candor.themethodic.com/docs/comment-thread.md).
Install: npx candor-ui add plan clarifying-questions step-list comment-thread
Read each item's docs before using it and take its props from there; don't guess them. Pro and Premium items need the person's licence key, which they add with `npx candor-ui key <key>`; don't ask for it.