memory_store
Persist a string value under a key to survive across sessions, with confirmation of new or overwritten writes. Use for preferences, agent memos, or named facts that need exact recall.
Instructions
Persist a string value under a key in ContextPulse's local memory database.
Returns confirmation with the stored key and an indication of whether the write was new or an overwrite.
USE WHEN: you need a value to survive across sessions and be recallable by exact key (preferences, agent memos, named facts). NOT FOR: fuzzy retrieval (use memory_search) or semantic similarity (use memory_semantic_search). For ephemeral session state, hold it in agent context — don't bloat persistent memory. ALTERNATIVES: route_to_journal (timestamped narrative log) is better for journaling.
BEHAVIOR: SIDE EFFECT — overwrites any existing value at the same key (last-write-wins). Persists to the local SQLite memory database; survives daemon restart. Idempotent for identical (key, value, tag) tuples. No auth or rate limits — local only.
PARAMETERS: key: stable identifier. ASCII recommended. Max 256 chars. Required. value: string to persist. Max ~1 MB. Required. tag: optional grouping label, queryable via memory_list(tag=...).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | ||
| value | Yes | ||
| tag | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |