Recall
crbro_recallSearch saved facts, decisions, patterns, preferences, errors, debts and maps from earlier sessions before answering questions about the user, projects or past work.
Instructions
Read-only search of everything saved in earlier sessions — facts, decisions, patterns, preferences, errors, debts and maps. Call it BEFORE answering anything about the user, their projects, preferences, decisions or past work: the answer is usually stored, and making them repeat it is the failure this memory exists to prevent. One result per neuron: the best matching entry with entry_id (read it whole: crbro_inspect view=neuron entries=[id]), matched_kind, matched_added, a confidence label (weak = little of the question covered; verify) and also_matched previews. Lines not the user's own carry origin, also_matched too: team: (team if unshared) with self-declared by, or miner. Rows past their shelf life move to possibly_stale as last_known with a next_step: check before answering with one, or say it may be out of date. If nothing matches, retry with 2-4 phrasings in queries or fewer, rarer words. has_map:true: read the system map with crbro_map before touching that system.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Only these entry kinds, e.g. ["error"] for past mistakes before repeating one, ["decision"] for what was agreed and why, ["debt"] for what was deferred. Day logs are left out when set. | |
| limit | No | Max neurons returned (default 5, ranked; ask for more only when the top five did not answer). | |
| query | Yes | What to look for, e.g. "Firebase authentication setup". Fewer, distinctive terms beat full sentences. | |
| since | No | Only entries recorded on or after this: a day ("2026-09-01") or a span back from today ("7d", "2w", "3m"). For "what changed lately" and to keep an old telling out. A later verification does not make an old entry new. Undated entries cannot prove they are recent: they are left out and counted in undated_skipped. | |
| domain | No | Only neurons in this domain (exact match, e.g. "proyectos-web"). Day logs have no domain: sessions_matched is listed regardless. | |
| queries | No | Alternative phrasings of the same question, searched together with query and fused by rank. Use synonyms, the other language and the concrete product name; 2-4 is plenty. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | Yes | ||
| query | Yes | ||
| filters | No | ||
| results | Yes | ||
| has_more | No | ||
| returned | No | Rows that came back: results plus possibly_stale | |
| truncated | No | ||
| stale_warning | No | Set, first, when some row moved to possibly_stale: do not answer with those as current | |
| total_results | Yes | ||
| possibly_stale | No | Rows whose best entry is past its shelf life since last verified: warning, next_step (what to check before answering), the entry as last_known instead of matching_content, then the rest of a results row plus age_days, last_verified, shelf_life, shelf_inferred | |
| sessions_total | No | ||
| matched_neurons | No | Neurons with any hit before limit; total_results is what came back | |
| undated_skipped | No | With since: matching entries left out for having no date | |
| sessions_matched | No | ||
| possibly_stale_count | No |