Skip to content

The screens an agent product needs

31 screens, from the chat to the audit log. Each has two or three ways to lay it out and a wireframe of each, the Candor items that build it, an install command, and a brief you can hand to a coding agent. Where a pattern already covers part of a screen, it links there.

Talking to the agent

Where a person and an agent work through a request together: the chat, the ask before acting, the plan, the copilot and the handoff to a person.

Approving and controlling

Where people decide what an agent may do and undo what it did: approvals, tool permissions, budgets and restore points.

Watching the work

Where people see what a run did, what it cost and what happened to it: run detail, traces, the console and the audit log.

Judging the output

Where people decide whether the agent is good enough: eval scorecards and the queue for grading real answers.

Knowledge and setup

Where the agent is configured and taught: its settings, what it knows, the servers it connects to, and who may change any of it.

The app around the agent

The frame that holds the rest: the shell and its session list, project workspaces, and what reaches people while they're away.