crewship consolidate
Trigger the Consolidate worker — the background process that compacts recent agent/crew journal activity into semantic rules appended to.memory/topics/learned-*.md. Normally runs on a 6h schedule; this command forces an immediate pass.
Subcommands
consolidate run honours the global --format flag (json/yaml/ndjson) — see
Output Formats.
crewship consolidate run
The command takes no positional args — scope is passed via flags. A bare
crewship consolidate run backend-team fails (unknown command).
Sample outputs:
accepted=true on a triggered run confirms the request was genuinely accepted (not just that a 202 came back). Accepted, but skipped (202) with a note means the consolidator is wired but lacks a summarizer client — set OLLAMA_HOST and install a chat model.
Requirements
- Auth:
OWNERorADMINrole (403 otherwise). - Ollama: The consolidator needs a summarizer LLM. In local dev, start Ollama with the external-SSD model path:
Errors
Journal entries emitted
Even when skipped, the run emits bothsystem.consolidation_triggered and system.consolidation_completed so the audit trail captures the no-op. See the Consolidate guide for payload shapes.
Related
- Consolidate guide.
- Consolidate API.
- Episodic memory — indexer runs on the same schedule.