Skip to main content

crbro-memory

Overview Schema Source Related Servers Discussions Admin

Consolidate the session

crbro_consolidate

Idempotent

Consolidate session knowledge before ending a conversation. Persists pending writes, logs summaries, links neurons, and syncs team spaces to prevent knowledge loss.

Instructions

Write: close the session — the only way to log a session. Call it before the conversation ends. Persists pending knowledge and index writes, logs the session from summary (credentials stripped, kinds in redacted), sets the context's last_session, recalculates heat, links the neurons written this session with weak temporal synapses (synapses_updated), updates the manifest and syncs shared team spaces (offline is normal). Returns session_id, facts_saved, decisions_saved, topics_touched and per-space sync state; topics_touched logs neurons you only read. promotion_candidates: own lessons (not from a teammate or the miner) found in 2+ project neurons, with suggested_target; nothing is moved. Not consolidating loses the session's knowledge. Mid-session open items go to crbro_context; housekeeping is crbro_maintenance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`summary`	Yes	A headline paragraph, not a report: what was done, decided and left open, in a few sentences. The facts themselves belong in crbro_learn, where recall finds them; this text is re-read at every boot. Stored whole, after credential redaction, and searchable by recall as a session hit (sessions_matched). Facts still belong in crbro_learn: a hit in a log is narrative, a fact answers.
`topics_touched`	No	Neuron ids this session used WITHOUT writing (recalled, inspected, discussed). Added to the log's topics_touched next to the ids written this session; write counters stay real. Unknown ids are dropped and listed in topics_unknown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.4.0Sep 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed1 schema field changedv2.2.0Sep 7, 2026

changedInput schema / properties / summary / description

Previous value: -"A headline paragraph, not a report: what was done, decided and left open, in a few sentences. The facts themselves belong in crbro_learn, where recall finds them; this text is re-read at every boot. Stored whole, after credential redaction. Session logs are not searched by recall: what only lives here is invisible to it."New value: +"A headline paragraph, not a report: what was done, decided and left open, in a few sentences. The facts themselves belong in crbro_learn, where recall finds them; this text is re-read at every boot. Stored whole, after credential redaction, and searchable by recall as a session hit (sessions_matched). Facts still belong in crbro_learn: a hit in a log is narrative, a fact answers."

Changed1 schema field changedv2.1.2Sep 7, 2026

changedInput schema / properties / summary / description

Previous value: -"A headline paragraph, not a report: what was done, decided and left open, in a few sentences. The facts themselves belong in crbro_learn, where recall finds them; this text is re-read at every boot. Stored after credential redaction; beyond 3,000 characters it is cut and the response says so."New value: +"A headline paragraph, not a report: what was done, decided and left open, in a few sentences. The facts themselves belong in crbro_learn, where recall finds them; this text is re-read at every boot. Stored whole, after credential redaction. Session logs are not searched by recall: what only lives here is invisible to it."

Changed1 schema field changedv2.1.0Sep 7, 2026

changedInput schema / properties / summary / description

Previous value: -"What was accomplished: concrete work, decisions, outcomes. Stored (after credential redaction) as the session log later sessions read."New value: +"A headline paragraph, not a report: what was done, decided and left open, in a few sentences. The facts themselves belong in crbro_learn, where recall finds them; this text is re-read at every boot. Stored after credential redaction; beyond 3,000 characters it is cut and the response says so."

Changed2 schema fields changedv2.0.0Sep 3, 2026

changedInput schema / properties / summary / description

Previous value: -"What was accomplished: concrete work, decisions, outcomes. Stored verbatim as the session log later sessions read."New value: +"What was accomplished: concrete work, decisions, outcomes. Stored (after credential redaction) as the session log later sessions read."

addedInput schema / properties / topics_touched

Added value: +{
+  "description": "Neuron ids this session used WITHOUT writing (recalled, inspected, discussed). Added to the log's topics_touched next to the ids written this session; write counters stay real. Unknown ids are dropped and listed in topics_unknown.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedv1.14.0Sep 3, 2026

changedInput schema / properties / summary / description

Previous value: -"Summary of the session being consolidated"New value: +"What was accomplished: concrete work, decisions, outcomes. Stored verbatim as the session log later sessions read."

First observedv1.4.0Aug 17, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare the safety profile (write, idempotent, non-destructive, open-world), while the description adds substantial behavioral detail the annotations cannot express: pending writes are flushed, the summary is redacted and stored whole, last_session/heat/manifest are mutated, weak temporal synapses are created, shared team spaces sync, and 'offline is normal'. It even enumerates the return payload and the promotion_candidates rule. No contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the write action and the single most important constraint, and nearly every clause carries distinct information (side effects, return fields, alternatives). It is dense and somewhat overpacked, but little is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-stakes terminal write with no output schema, the description covers the side effects, the redaction behavior, the loss-of-knowledge consequence of skipping it, the returned fields, and the sibling alternatives. An agent has everything needed to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already fully documented, making 3 the baseline. The description restates that topics_touched logs read-only neurons and that summary is re-read at every boot, which largely duplicates the schema text rather than adding syntax or format detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('close the session', 'the only way to log a session') and immediately scopes it against siblings by routing mid-session open items to crbro_context and housekeeping to crbro_maintenance. An agent can distinguish this from every other crbro_* tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Call it before the conversation ends'), a cost for failing to call it ('Not consolidating loses the session's knowledge'), and names the two alternatives (crbro_context, crbro_maintenance) with the conditions that select them. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools