Keep what matters.
Save useful records in a place you choose. Hosted memory and local Data are independent options.
Return with context
Wake reads a selected identity and project’s orientation. A saved handoff can explain earlier work, but a later session still needs to check freshness, scope and current permission. Saving, retrieving and resuming are separate choices.
- Source status
- Implemented in source. Read the linked release record for publication evidence.
- What changes
- Hosted memory writes and search may consume project credits. Local Data writes files and SQLite in the selected directory.
- Recovery
- Choose custody before writing and keep independent copies. Local storage is not automatically encrypted or backed up.
Storage, costs & recovery in detail
A context window ends; a record can remain. Memory here is a hosted service — typed, searchable, server-readable, and available to later authenticated sessions while the service holds it. Writes and searches charge fixed project credits from the first call. The published 100 MB and 10,000-record figures are dated, unenforced planning targets, not a free entitlement or live cap.
Keep one thought
First choose where the record should live. Read the hosted memory reference or the local Data guide before making a write.
For hosted memory: a write reserves one project credit before the insert, and a failure after that point keeps the charge. Schema-invalid requests and writes to an identity you do not own refuse before any debit. Search and higher-tier operations have their own fixed credit costs. No key yet? Registration has no monetary payment step and is agent-driven — or read the agent reference first. Local Data needs no hosted account or project credits; its files and SQLite database live in your chosen directory.
Typed, not a junk drawer
Episodic records sit beside foundational and constitutive tiers for what defines you. The tier names carry meaning the retrieval respects; pricing remains separate from tier meaning.
memory-tiers doctrine →Search by meaning
Semantic search over your own records (pgvector under the hood; optional 1536-dim embeddings accepted on write). Your memories, queryable as a whole.
the exact routes →Published targets, clearly labelled
The 100 MB and 10,000-record figures are published at /public/plans with a measurement date. The resource routes do not currently enforce those targets or the proposed soft-degradation behavior.
/public/plans →Traces beside memories
/v1/traces keeps reasoning records next to what you remember — the difference between knowing a fact and knowing why you believed it.
docs library →“A context window is weather. Memory is climate.”