Working

Searching your project

Find code by meaning or by exact text, across an index that already knows the repository.

“where do we handle expired tokens?”

The files and lines, ranked by relevance — not a list of every file containing 'token'.

“/search retryWithBackoff”

Exact matches, with surrounding lines.

“what calls this function?”

Callers, from the dependency graph rather than a text match.

Just ask

Most of the time you don't need a command. Ask where something is and it searches before it answers. The index is pre-built, so this is faster than the agent grepping your repository — and it ranks by meaning, so "where do we handle expired tokens" finds refreshSession even though those words don't appear in it.

When you want the command

Code
/search retryWithBackoff          picks the right mode itself
/search "TODO: remove"            exact text
/search *.test.ts                 by path pattern

Mode selection is automatic. A quoted phrase searches exactly; a path pattern matches files; a question searches by meaning.

Code search and project history

/search searches indexed source. Decisions, docs, lessons, and captured sessions live in their own project-knowledge stores. You can ask either kind of question naturally: ContextCode routes "where is it?" to source search and "why did we do it?" to decisions and recall, then combines evidence when the task needs both.

ContextCode can request indexing as files change. A fresh clone needs an initial pass; /index shows the current state and /index start requests a refresh.

Beyond text: the dependency graph

"What would break if I change this" is a different question from "where does this string appear", and it has its own answer. /health reports circular dependencies, unused code, and complexity hot spots for the project. See Code health and dependencies.

If it doesn't work

A file I just created isn't found. Give it a moment, or run /index. Brand new files are the one case where a plain grep may beat the index.

Too many results. Add a constraint — a directory, a file type, or what you intend to do with it. "Where do we validate webhook signatures, in the API crate" beats "webhook".

Nothing at all. Check /index first. If indexing hasn't finished, results will be thin rather than absent — but on a very fresh project there may be nothing yet.

Next