UnisonHow do I limit recall to a specific folder or team?
Use pathPrefix to scope Unison recall to a particular path, preventing irrelevant sections of the brain from diluting results.
How do I make recall only search within a specific folder or team namespace?
Pass pathPrefix to GET /v1/brain/context. The brain will only consider pages whose path starts with that prefix, which improves ranking precision and keeps unrelated content from diluting results.
Examples
Search only within your private notes:
GET /v1/brain/context?q=auth+decisions&pathPrefix=/private/notes/Search only within a team's namespace:
GET /v1/brain/context?q=sprint+goals&pathPrefix=/workspace/teams/platform/Search within workspace-wide shared knowledge:
GET /v1/brain/context?q=company+values&pathPrefix=/workspace/When to use it
- Multi-tenant apps: Scope each user's recall to their own actor path.
- Noisy workspaces: If a large workspace has many teams, scoping to the relevant team reduces noise significantly.
- Hybrid retrieval: Run two parallel recall calls — one scoped to
/private/for personal context, one to/workspace/for shared knowledge — then merge the results before injecting into the prompt.
When not to use it
Don't over-scope. If you're not sure where a fact lives, omit pathPrefix and let the brain search everything. You can always add it later once you've profiled where your relevant content actually is.
See also: Private vs workspace vs team scoping.
How do I improve the quality of what the brain returns?
Practical steps to get better recall from the Unison brain: ingest more, write clearer facts, use the right mode, and scope your queries.
What's the difference between /private/, /workspace/, and /workspace/teams/<slug>/ paths?
Understand the three memory scopes in Unison: private (caller-only), workspace (all members), and team (a sub-group).