remember
Store important context, decisions, and preferences in long-term memory for recall across sessions. Optionally checks for similar existing memories and sensitive data before saving.
Instructions
Store information in long-term memory within a specific space. Use this proactively to save architecture decisions, user preferences, project conventions, bug solutions, and key context. Content is scanned for sensitive patterns (API keys, passwords, tokens) before sending to Cloud. If detected, the write is blocked and findings are returned with a hint on how to proceed. For chat:* spaces, similar existing memories are checked automatically and surfaced as conflicts in the response. Use check_conflicts to override. Content is queued for AI extraction and becomes searchable only after upstream processing completes. For important writes, prefer remember(include_status=true) so the write-after status check runs immediately. Use request_status, recall, or briefing to distinguish queued, provisional, fallback, and searchable states. Set flush=true at end of session or topic switch; flush=false during ongoing work. Provide a description when creating a new space for the first time.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Message role: 'user' or 'assistant' | |
| flush | No | Whether to trigger immediate extraction. Default true. Set false only when sending multiple messages in a batch | |
| sender | No | Backward-compatible alias. Use 'user'/'assistant' as role alias, or pass a sender user_id | user |
| content | Yes | The information to remember | |
| user_id | No | Optional sender user_id override (API sender field) | |
| space_id | No | Target memory space in <domain>:<slug> format (e.g. coding:my-app, chat:preferences, chat:daily, study:ml). Use chat:preferences for durable personal preferences, chat:daily for ongoing chat context, coding:<repo> for project decisions, and study:<topic> for learning notes. If omitted, the server may use EVERMEMOS_DEFAULT_SPACE or auto-detect from the current git remote (coding:<repo-name>). | |
| refer_list | No | Optional referenced message ID list | |
| description | No | Human-readable description of this space (recommended when creating a new space) | |
| include_status | No | Whether to also query request status once after queuing the memory write. Recommended for important writes and write-after checks | |
| check_conflicts | No | Check for similar existing memories before storing. Default: auto (enabled for chat:* spaces, disabled for others). When conflicts are found, the new memory is still stored and conflicts are returned for the agent to decide. |