v0.7.0:
remember replaces the previous remember + update_memory + forget tools. Mode is auto-detected from params.Modes
Create (default)
Provideentity_name + entity_kind + layer + content:
Update
Providememory_id + fields to change:
memory_id and session_file_edits links. Preferred over delete + create.
Delete
Setforget: true + memory_id:
Parameters
Create mode (required)
Name of the entity this memory is about (e.g. “MyProject”, “Supabase”, “Alice”).
One of:
person, company, project, concept, file, other.Memory layer. One of:
goal, context, emotion, implementation, caveat, learning.Common aliases are accepted:| Alias | Resolves to |
|---|---|
why, intent, targets | goal |
background, reason, timing | context |
tone, feelings, mood | emotion |
impl, how, tried | implementation |
warning, pain, pitfall, dont | caveat |
decision, insight, growth | learning |
The memory content. Plain text or JSON with structured axes (title, altitude, type, state, what, why, affects, next_action).
Optional (all modes)
0.0 to 1.0. Set to 0.9 or higher to pin a memory — pinned memories are protected from auto-forgetting even outside the caveat layer. Default: auto-assigned based on layer.Optional thread ID to group related memories (e.g. a session ID or decision chain). Enables decision -> implementation -> outcome tracing.
Bypass the paste-back quality check. Set
true only when you are sure the content is original user or agent thought, not pasted CI logs or assistant output.Update mode
The
memory.id to update. Get this from a prior recall response. When provided without forget: true, enters update mode.Delete mode
Set
true with a memory_id to delete that memory.Behavior
- Entity resolution: 3-tier matching — canonical_key exact -> normalized_name -> case-insensitive name -> insert new entity
- Quality check: Rejects pasted CI logs, assistant output, and other non-original content (bypass with
force: true) - Auto-structuring: Plain text is wrapped into structured JSON with inferred
altitude,type, andstateclassifications - Pinning: Memories with
importance >= 0.9getprotected = 1, preventing auto-forgetting - Events: Records a
memory_storedevent for momentum tracking
Migration from pre-v0.7
| Old call | New equivalent |
|---|---|
update_memory({ memory_id: 42, content: "..." }) | remember({ memory_id: 42, content: "..." }) |
forget({ memory_id: 42 }) | remember({ forget: true, memory_id: 42 }) |
forget({ dry_run: true }) | No longer exposed — auto-consolidation handles cleanup on startup |