Memory
Jarvis keeps a long-term memory in EAM and recalls it on every turn.
How recall works
Each chat or voice turn, Jarvis searches EAM for the few memories that matter and adds them to the prompt as user data. If EAM is slow (over 300 ms) a local word-overlap search over the memories already loaded answers instead, and the EAM result is kept for the next turn.
What gets saved
| Kind | When |
|---|---|
| Explicit | "Remember that…" or "lembra que…". Saved before Jarvis replies, and Jarvis only says it is saved after EAM confirms. |
| Automatic | First-person facts, preferences, decisions and tasks, after a reply. At most one every 15 seconds and 25 per session. |
| Outcomes | Reminders you create (switch in Tasks) and emails you send (recipient and subject, never the body). |
| Summaries | A finished conversation of three or more of your turns gets a short summary. |
Secrets, passwords and sensitive categories (GDPR Article 9) are never saved. A new value for the same attribute ("my car is…") replaces the old one.
The Memory screen
⌘3 opens the memory graph: search, filter by kind, click a node to read, edit or delete. Deleting asks for confirmation. Options turns recall and auto-saving off.
Import from this Mac
Memory, then Import from this Mac, can import your own prompts from Claude Code, Kiro, Cursor and your shell history. Every source is off by default. Secrets are redacted on your Mac before anything is sent, and you can preview locally first. Import needs the EAM import API to be available; the screen says when it is not.
Account
Memory uses your Jarvis sign-in. Signing out of Jarvis disconnects EAM. The same memories appear in the EAM web app.