memory_reconcile_candidates
Returns clustered memory candidates, direction-layer inventory, and promotion material so an agent can judge merges, invalidations, and keeps before applying batch memory reconciliation.
Instructions
On-demand organization · coarse screening: returns episodic-layer candidate groups + the direction-layer inventory + distillation material + operating instructions.
Memory organization = an explicit on-demand in-session action (CC is not resident; there is no background organization process). This tool performs only deterministic coarse screening (zero LLM) — the OS has no independent LLM credentials, so the judgment is made by you (the in-session agent calling the tool); the tool is responsible only for candidate coarse screening and operation application ("the agent computes, the tool stores").
Returns four blocks (project_id is automatically resolved from the current context):
candidate_groups: valid task_memos clustered by scope_path/task, with in-cluster BM25 pairwise similarity above the threshold paired into candidate groups (including each entry's full text + id). Make an LLM fine judgment per group: KEEP (keep all) / MERGE / INVALIDATE (contradiction invalidation) / NOOP (no action).
direction_inventory: the full text of all valid direction-layer entries — perform a staleness check on each (a referenced feature retired / version outdated / the world changed → propose invalidate).
promotion_candidates: high-frequency clusters recurring across tasks — material for distilling into direction-layer entries (the promote operation; source_refs point back to the source memos).
operation_guide: the four operations' semantics + the three reconcile rules (keep only the high-frequency and useful / point to the authoritative source rather than restating / prefer concise rewrites) + the hint to open ultracode when the volume is large.
After judging, hand the confirmed operations to memory_reconcile_apply for batch application.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "memory_reconcile_candidates"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| threshold | No | the in-cluster BM25 similarity pairing threshold (0-1, default 0.45) | |
| scope_path | No | organize only that path scope's memos (empty = the whole project's valid memos) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||