Screens / The app around the agent

Project workspace

Give each project a conversation with an agent team, and show which projects need the person.

For: People who run several pieces of agent work at once.

Markdown

2 ways to lay it out

1. Projects rail and conversation

Pick it when: The default: projects are conversations, grouped by what needs the person.

A rail of projects grouped by what needs you, the selected project's thread in the middle, the team on the right.

Project workspacePremiumA workspace where each project is a conversation with an agent team, grouped by what needs the person.
Agent activityProWho is working right now, in words.
Run treeProWho handed work to whom.
Task trayProBackground work as one pill.
PresenceProWho else has the project open now, people and agents, and what each is doing.

Install projects rail and conversation

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

2. Board of projects

Pick it when: Many projects at different stages; the person triages.

Columns by state with a card per project.

Project workspacePremiumThe grouping, as columns.
InboxProEverything with something for the person.

Install board of projects

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

Rules that matter most here

The agent is always named, by the app
Each message and each step names which agent in the team did it.
Unknown stays unknown
A project whose agents have gone quiet shows when it was last heard from.
A control that can't be used says why
A project the person can see but not change says why.

Already covered elsewhere

Builds the whole screen with an agent route and a store: Project workspace (Premium), with a -claude twin for the Claude Agent SDK.

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 project workspace with Candor UI. Start from the project-workspace template (project-workspace-claude for the Claude Agent SDK): each project is a conversation with an agent team.
The rail groups projects by what needs the person: waiting on you, running, done.
Show who is working with AgentActivity and who handed work to whom with RunTree; use TaskTray for background work.
Name the agent on each message and step from your records.
A project whose agents have gone quiet shows when it was last heard from.
A project the person can see but not change keeps its controls and says why (Locked).

Start from the "Projects rail and conversation" layout: A rail of projects grouped by what needs you, the selected project's thread in the middle, the team on the right.
Candor items: project-workspace (https://candor.themethodic.com/docs/project-workspace.md), agent-activity (https://candor.themethodic.com/docs/agent-activity.md), run-tree (https://candor.themethodic.com/docs/run-tree.md), task-tray (https://candor.themethodic.com/docs/task-tray.md), presence (https://candor.themethodic.com/docs/presence.md).
Install: npx candor-ui add project-workspace agent-activity run-tree task-tray presence
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.