Skip to content
CommandChain CommandChain CommandChain Docs

Search what the workspace knows

Knowledge search answers “have we already worked this out?” from your own workspace: meetings, tasks, summaries, artifacts, research findings, and indexed repository files.

Where it appears

Section titled “Where it appears”

There is no search box of its own. Knowledge search is a tool agents use, on three surfaces:

  • With Eva. Ask her a question about your own work and she searches the corpus to answer it, quoting what she read.
  • In meetings. An agent that needs to know what was decided before, or whether something already exists, searches rather than guessing or asking you.
  • In coding runs. The coding agent on a runner reaches the same corpus through a small local shim, so it can check for an existing implementation before writing a new one. See knowledge in runs.

Because it is a tool rather than a page, the way to use it is to ask a question that needs it: “what did we decide about offline caching”, “has anyone looked at trail conditions staleness”, “where is the tile eviction rule written down”.

What it can see

Section titled “What it can see”

Everything the workspace has produced, indexed as work happens rather than on a schedule:

  • meeting messages and meeting summaries,
  • tasks and their specs,
  • workspace items, artifacts, and research findings,
  • content assets,
  • repository files, for repositories that have been indexed.

Results are ranked by relevance rather than recency, and each one carries what it came from, so an answer can be traced back to the meeting or task that said it.

What it cannot see

Section titled “What it cannot see”
  • Anything outside your workspace. A search never crosses into another workspace’s corpus. For questions about the outside world, use a research job.
  • Anything deleted. Removing the source removes its passages.
  • Secrets and environment values. Those are never indexed.

When a search comes back empty

Section titled “When a search comes back empty”

An empty result means the corpus has nothing on the question, which is a real answer: it usually means the thing was decided in a channel outside CommandChain. It does not mean the search is broken, and agents are told to treat it that way rather than inventing an answer.

Next steps

Section titled “Next steps”