Create Memory Checkpoint
engram_reflectCheckpoint a milestone or handoff for later recovery with engram_rehydrate. Supply at least one of summary, learnings, used_memories or feedback. Returns Markdown with stored/skipped counts, outcomes and next actions. Use engram_store for one lesson and engram_report_outcome for one outcome.
store=false skips learning storage only: the journal and supplied outcomes/feedback can still be written. This checkpoint leaves the session open. Retrying may duplicate writes; verify prior success first. Consumes workspace daily call quota and memory quota for saved lessons. OAuth: session:write, memory:write and outcome:write.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | No | Repository slug, e.g. engram or billing-api, within the authenticated workspace. This is a memory filter, not a filesystem path or workspace selector. | |
| task | No | Concrete current goal or decision, e.g. diagnose checkout retries; used to focus context and session recovery. | |
| store | No | Default true saves accepted durable learnings; false skips learning storage only. Session checkpoints, supplied outcomes and feedback are still recorded. | |
| summary | No | Milestone/handoff summary: what changed, evidence, decisions and remaining work. Required unless learnings, outcomes or feedback are supplied. | |
| feedback | No | Optional product feedback or feedback-pulse dismissal; separate from outcomes about individual memories. | |
| learnings | No | Durable private workspace lessons to persist when store=true; only the first 8 are processed. Low-quality entries may be skipped. The summary remains a journal checkpoint. | |
| agent_tool | No | Calling client name for attribution, e.g. codex, claude-code, cursor, or gemini. Omit if unknown. | |
| session_id | No | Exact journal id from start/rehydrate/list_sessions. Disambiguates parallel work; writing requires your active session. Rehydrate may read shared or closed history. | |
| used_memories | No | Outcomes for memories actually used during this milestone; only the first 20 are processed. Omit when none were applied. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The same bounded payload as content[0].text; interpret it using format. JSON text contains the endpoint-specific fields described by this tool. | |
| format | Yes | Payload encoding: Markdown context/checkpoint, serialized JSON data, or plain confirmation text. | |
| truncated | Yes | True when the payload exceeded 120,000 characters and was cut with a notice. Narrow the request; truncated JSON is not parseable. |