Skip to main content

What it does

Creates a manual Memory Checkpoint: a bounded backup of durable memory for later review and recovery planning. Use this only when the user explicitly asks to create a checkpoint or backup. Automatic conversation provenance is stored separately as Conversation Snapshots and does not consume checkpoint allowance. Checkpoint creation is intentionally cheap: it uses bounded indexed reads and document writes only. It does not run LLM summarization, embeddings, vector search, graph enrichment, or raw file backup.

Parameters

Returns (Create mode)

Returns (List mode)

Field descriptions:
  • checkpointId — Unique identifier for the checkpoint
  • label — Human-readable name
  • createdAt — Unix milliseconds when checkpoint was created
  • memoryCount — Number of memories included in the checkpoint
  • allowance — Number of retained Memory Checkpoints allowed by the current plan
  • retainedCount — Current number of retained Memory Checkpoints
  • snapshotCap — Maximum memory entries considered for each checkpoint on the current plan
  • tags — Optional tags for filtering and organization

Examples

Basic usage

Advanced usage

When to use this vs alternatives

  • crystal_checkpoint — When the user explicitly asks to save a manual Memory Checkpoint
  • crystal_capture — When you want to save a single memory immediately
  • crystal_recent — When you need to see recent conversation messages, not checkpoint history

Error handling

Notes

  • Checkpoints are retained according to plan allowance: Free 1, Starter/Pro 5, Ultra 10, Unlimited 20
  • Delete an older checkpoint before creating another at the allowance limit
  • Labels should be descriptive and action-oriented (✅ “Implemented vector search” vs ❌ “checkpoint 42”)
  • Tags are lightweight and support filtering checkpoints by theme or project
  • Scoping by session, channel, or explicit memoryIds lets you create focused checkpoints when supported by the caller
  • List mode supports pagination via limit parameter
  • Checkpoints are useful before risky changes only when the user explicitly asks to create one
  • Use descriptions to explain WHY a checkpoint was created or what state it represents
  • Conversation Snapshots are separate automatic provenance records and are not listed as Memory Checkpoints