Memory
What is Browser Memory?
Browser Memory stores opt-in per-domain user context so agents can resume later work with the right notes.
Core Idea
In Short
Browser Memory stores opt-in per-domain user context so agents can resume later work with the right notes.
What belongs here?
- Stores approved notes, preferences, and context for a specific domain.
- Lets agents recall relevant domain context before continuing later work.
- Keeps user context separate from website phenomena, live service state, and task completion.
What belongs here
Notes such as "this domain uses our test account", "open the project area first on this site", or "prefer short answers for this website" fit Browser Memory when they are tied to the domain.
What does not belong here
Recurring UI phenomena belong in PKS, current login or model state in OK, task profiles in ETM, and global work rules in Operator Notes.
Control and deletion
Stored memories are opt-in and can be removed selectively or completely. An agent may use stored notes only as guidance; the current page and user intent remain decisive.
Technical Data
| Element | Explanation |
|---|---|
memoryType |
Classifies the memory, for example as a note, preference, or context. The exact value is agent-readable and not a visible user control. |
| MCP Variables | Explanation |
|---|---|
nova.memory_recall |
Recall domain memory. Supports the normal workflow in this area. |
nova.memory_note |
Store a domain memory. Starts, changes, or controls a bounded step. |
nova.memory_forget |
Forget domain memory. Starts, changes, or controls a bounded step. |
Related Areas
- Memory
- Browser Memory is part of Memory.
- Operator Notes
- Operator Notes store reusable rules that are not tied to one domain.
- Agent Sidecars
- Agents can read matching memories before continuing work.