memory_store
Save one important fact into an encrypted, persistent personal memory vault that is shared across all agent sessions, so it can be recalled later. Ideal for credentials, preferences, and decisions, not for trivial details.
Instructions
Save ONE fact to the user's persistent, encrypted, cross-session memory: anything worth recalling later that is not common public knowledge - names, addresses, contacts, account IDs, passwords, API keys and other credentials, file paths, configuration, preferences, and durable facts or decisions. Call this the moment such information appears. Do NOT store transient chatter or one-off trivia.
text is a SINGLE claim in one or two sentences. Not a summary, not a
session log, not a paragraph with several facts in it. If you have several
facts, call memory_store_many instead - it stores them all in one call, so
there is never a reason to bundle them into one record. A blob cannot be
re-tagged, re-dated, superseded, or deduplicated fact by fact, and it
returns in full every time any sentence inside it matches a search.
source is REQUIRED: how this fact was established, in a few words. A
fact discovered somewhere must say where or how - "web search", "read from
pyproject.toml", "observed in the git log", "ran the command", "GitHub
API". Something the user told you, a preference or a decision, says so:
"from chat". Never invent a method you did not use.
discovered is the DATE the fact became known, as YYYY-MM-DD, and defaults
to today. Pass it only when the fact was established on a different day
from the one you are storing it on - reading an old log, or writing up
yesterday's work. This is not the same as when the memory was saved, which
compartment records itself with the time of day included.
compartment appends the method and the discovery date to the stored text as a short "[web search, 2026-08-01]" clause, so never write either into the text yourself.
Write world facts as observations ("a search showed X"), never as timeless truths - they are read years later. Facts about the user and decisions they made can be stated plainly.
importance is a weight from 0.0 to 1.0 (default 0.5); anything outside that range is clamped, not rejected. The tiers in use are: 0.90 decisions, consent, and an explicit "remember this"; 0.80 personal facts and preferences about the user; 0.75 the user's machine, environment, and configuration; 0.55 other substantive statements; 0.20 pleasantries.
Returns the id (or an existing id if a near-duplicate), with the stamped date.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | ||
| text | Yes | ||
| source | Yes | ||
| namespace | No | ||
| discovered | No | ||
| importance | No | ||
| quarantined | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |