Screens / Knowledge and setup
Agent roster and settings
See every agent on the team, and change one agent's model, instructions, tools and schedule, with a history of changes.
For: Admins and agent owners.
3 ways to lay it out
1. Roster, then a settings page
Pick it when: The default: the roster is a table; each agent has its own settings page.
- Agent rosterProEvery agent on the team: role, model, whether it's on, and two weeks of runs.
- Settings layoutProGrouped sections down the side and the open one beside them.
- Model settingsProWhich model an agent uses and how hard it thinks.
- Instructions editorProStanding instructions, with variables filled in per run.
- Tool permissionsProPer tool: always, ask first or never.
Pro and Premium items need a licence key; free ones install as they are.
2. Cards with a drawer
Pick it when: A small team of agents where the faces matter and settings are quick.
- Agent rosterProThe agents.
- Agent avatarFreeA glyph and hue by role.
- Side panelProThe settings drawer.
- Permission modeProThe mode, with what it lets the agent do.
Pro and Premium items need a licence key; free ones install as they are.
3. Settings with versions
Pick it when: Instructions and tools change often and people need to see what changed and go back.
- Instructions editorProThe editor.
- Version historyProLive, draft and past versions, newest first.
- Schedule listProRecurring jobs, in plain words.
- Agent adminPremiumThe block: tools, model, versioned instructions and the routes that save them.
Pro and Premium items need a licence key; free ones install as they are.
Rules that matter most here
- A control that can't be used says why
A setting this person can't change shows its value and says why.
- Say what can and can't be undone
Publishing instructions says which version goes live and that the last one stays in history.
- The agent is always named, by the app
Each agent has the name and role your app gave it; the model doesn't choose its own.
Already covered elsewhere
- Builds the whole screen with an agent route and a store: Agent admin (Premium), with a
-claudetwin 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 an agent roster and settings with Candor UI. Start from the agent-admin block (agent-admin-claude for the Claude Agent SDK) for the routes that save changes.
AgentRoster lists every agent with its role, model, on or off, and two weeks of runs. Open an agent in SettingsLayout.
Sections: ModelSettings, InstructionsEditor (with variables like {{workspace.name}}), ToolPermissions and ScheduleList.
VersionHistory shows live, draft and past versions; publishing says which version goes live and the earlier one stays available.
Wrap a setting this person can't change in Locked so it shows why.
Name agents from your app's data (AgentAvatar), never from the model.
A new tool starts as ask first.
Start from the "Roster, then a settings page" layout: A roster table of agents with role, model and a two-week run strip; beside it, the open agent's settings in sections.
Candor items: agent-roster (https://candor.themethodic.com/docs/agent-roster.md), settings-layout (https://candor.themethodic.com/docs/settings-layout.md), model-settings (https://candor.themethodic.com/docs/model-settings.md), instructions-editor (https://candor.themethodic.com/docs/instructions-editor.md), tool-permissions (https://candor.themethodic.com/docs/tool-permissions.md).
Install: npx candor-ui add agent-roster settings-layout model-settings instructions-editor tool-permissions
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.