remember
Save facts, decisions, or preferences to persistent memory that retains across agent sessions. Encrypts content and generates vector embeddings for semantic search.
Instructions
Store a fact, decision, or preference in persistent memory so it survives across sessions. This is a write operation that creates a new memory record, encrypts the content at rest, and generates a vector embedding for semantic search. Use remember (not recall) when you learn something worth keeping: architecture decisions, user preferences, bug root causes, project conventions, or task outcomes. Do not use for ephemeral scratch data, secrets, or large files. Returns the memory ID and timestamp. Costs 1 operation against the API key's monthly quota (500 free, then paid). Use forget to delete outdated memories before storing corrections, to prevent contradictions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The information to store. Write as a complete, self-contained statement (not fragments). Include context: 'User prefers TypeScript for backend services' not just 'TypeScript'. Max 10,000 characters. | |
| agent_id | No | Unique identifier for this agent instance. Use a consistent value across sessions so memories are retrievable. Default: 'default'. | default |
| user_id | No | User identifier, required when scope is 'user'. Links the memory to a specific user across all their agents. | |
| tags | No | Categorical labels for filtering during recall. Use lowercase, consistent terms: 'preference', 'decision', 'architecture', 'bug-fix'. Max 20 tags, each max 100 chars. | |
| scope | No | Visibility: 'agent' (only this agent sees it, default), 'user' (all agents for this user, requires user_id), 'org' (all agents in the organization, requires org membership). | agent |