Screens / Knowledge and setup
Knowledge base and retrieval
Show what the agent knows, where it came from and how fresh it is, and let people see the passages behind an answer.
For: Knowledge owners, and anyone who wants to check an answer.
3 ways to lay it out
1. Sources and freshness
Pick it when: Owners add, review and retire what the agent can use.
- Knowledge sourcesProWhere the knowledge comes from, grouped by door.
- Source ingestProAdd knowledge: drop files, paste a link, or paste text.
- Freshness stampProHow old a piece of knowledge is.
- Prose diffProAn agent's rewrite of a page, word by word against the original.
Pro and Premium items need a licence key; free ones install as they are.
2. Retrieval inspector beside the answer
Pick it when: Someone must check an answer against its sources, such as a reviewer or an engineer tuning retrieval.
- Retrieval inspectorProThe passages behind an answer, in the order the retriever ranked them.
- CitationFreeAn inline [n] that opens its source.
- Confidence markProHow sure the system is, with what it rests on.
- Provenance traceProWhere a piece of information came from.
Pro and Premium items need a licence key; free ones install as they are.
3. What the agent remembers
Pick it when: The agent learns from the account's people and they need to see and correct it.
- Memory managerProWhat agents remember about this account, one line each, with who taught it and when.
- Memory modeProOn, paused or off, with what each does to memories already kept.
- Memory usedProThe line under a reply saying what it remembered.
Pro and Premium items need a licence key; free ones install as they are.
Rules that matter most here
- Unknown stays unknown
When no source covers the question the answer says it doesn't know; a source with no date shows no age.
- Reasoning is believed, not verified
Confidence is shown with what it rests on, not as a bare percentage.
- Say what can and can't be undone
Deleting a source says which answers it will no longer back.
Already covered elsewhere
- Builds the whole screen with an agent route and a store: Knowledge base (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 a knowledge screen with Candor UI. Start from the knowledge-base block (knowledge-base-claude for the Claude Agent SDK): an agent answers only from published articles, cites each article and version, and says when it doesn't know. KnowledgeSources lists where the knowledge comes from; SourceIngest adds files, links or pasted text; FreshnessStamp shows how old each piece is. Next to an answer, RetrievalInspector shows the passages in the order the retriever ranked them. Cite with Citation; show ConfidenceMark with what it rests on. When no source covers a question, the answer says so. A source with no date shows no age. For memory use MemoryManager, MemoryMode and MemoryUsed; deleting a memory says what it was used for. Start from the "Sources and freshness" layout: Sources grouped by where they come from, each with a freshness stamp, and an add box. Candor items: knowledge-sources (https://candor.themethodic.com/docs/knowledge-sources.md), source-ingest (https://candor.themethodic.com/docs/source-ingest.md), freshness-stamp (https://candor.themethodic.com/docs/freshness-stamp.md), prose-diff (https://candor.themethodic.com/docs/prose-diff.md). Install: npx candor-ui add knowledge-sources source-ingest freshness-stamp prose-diff 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.