What the app remembers
What you'll get. How context follows you between conversations, how to look at it, and how to delete a piece of it.
Nobody wants to re-explain their job every morning. AERIS Node is the app's memory: it organises what E:Voice already knows about your projects, agents, docs and decisions into something an agent can read before it answers.
The app describes it as a “Semantic knowledge graph for projects, agents, docs, decisions, and app memory”, and it is careful about the boundary: “Local hierarchy works without provider compute.”
Looking at what it knows
The Memory page — titled AERIS Node Memory — is on the Tools page of the tab bar, or from Settings under “Setup & tool shortcuts”. It opens in Visual Graph view; the menu switches to List.
List view sorts everything into seven groups you can open one at a time:
- Projects — project seeds, trackers and local project memory
- Agents — the identities available to E:Voice
- Docs — docs, receipts and references agents can cite
- Tasks / Pulse — the task board and work envelopes
- Decisions — accepted directions and durable choices
- Preferences — how you like things done
- Recent Events — safe operational events and receipts
Open an entry and you get its summary, where it came from, when it changed, what it connects to, and an Advanced toggle for the raw record.
Deleting something
- Switch to List view. The delete controls are not in the graph.
- Open the category, then tap the entry to expand it.
- Tap Delete. There is a Pin button next to it for the opposite problem.
Durable profile facts — the things the app has learned about you personally — work differently. They live in their own card, split into Visible memories and Suppressed / restorable, and the buttons are Suppress and Restore rather than delete. Each one shows its source, provenance, receipt and confidence, so you can see why it thinks that.
Not every entry can be deleted. Entries the app derives rather than stores — built-in agents, journal projections, some seeded records — show Read only and a greyed-out Delete. What you can delete, you can delete one at a time.
There is no memory editor. You can pin, delete and suppress. Rewording an entry means asking an agent to correct it; the label “Edit through memory tools” is telling you that, not offering you a text box.
Clear Context is not delete
This one catches people out. “Clear Context resets this chat's active context. It does not delete AERIS Node memory. Base memory can still be used later when relevant.” If you want something genuinely gone, go to the Memory page.
Turning AERIS Node off doesn't erase anything either — “Disabled stops new graph writes and indexing but does not delete existing AERIS Node entries.”
Local, or with provider help
Under Settings → Memory & data → AERIS Node Memory there's a Semantic indexing dropdown with three choices:
- Local only (the default) — “Uses local hierarchy and metadata only. No provider compute is called.”
- Use ChatGPT account — uses your signed-in OpenAI session when it's available.
- Use API key — uses a key from the vault.
If the status line reads “Selected but compute off”, you have picked a model but left indexing on Local only. Nothing is being sent anywhere.
On the same screen, Agent memory access starts on All agents — meaning trusted paired external agents can receive bounded, redacted memory context. Switch it to Local agents only and paired external agents get none. Both are legitimate; you should just know which one you're on.
What the last answer actually used
The Attached To Last Response card shows the injection trace for the most recent reply, with pills for the provider, boundary and vector path. It also draws the line most memory features blur: “Stored graph memory below is not the same as injected response memory.” What is stored and what got sent are two different questions, and this card answers the second one.
Recent work made the answers less repetitive: weakly relevant facts used in either of the last two turns get pushed down so they stop resurfacing, while strongly relevant ones still come through when the conversation needs them. Nothing was deleted to achieve that — it's a change in what gets picked.
Syncing with a desktop
AERIS OS pairing is optional and lives in Settings → Connections → AERIS OS Pairing. Scan the QR from AERIS OS, or paste its setup link. When it's connected you get Sync now and Forget pairing.
Unpairing is described exactly, in both directions: “Synced history stays on this phone; sync stops.” There are two versions — a full unpair that also asks the desktop to drop this phone's trust, and a local-only Forget for when the desktop can't be reached. The control stays available even when things are broken, deliberately, so a failed unpair is never a trap.
It does not delete anything on the desktop. Unpairing stops future sync. What is already over there stays over there.