Agent memory
Optional, private, off by default. Let the Sup agent remember useful facts about you across chats — encrypted, owned by you, and only ever on when you turn it on.
By default the agent is stateless: each conversation starts fresh. Turn on memory and it can carry a little durable context between sessions — your preferences, goals, and guardrails — so you don't repeat yourself. It stays in your account on Sup's own storage, and you can list or delete it any time.
#What it remembers
Memory keeps short, distilled facts, not your chat logs — things like:
- "prefers low-risk strategies"
- "trades SOL and SUI perps, ≤3x leverage"
- how you like explanations phrased
It is not for secrets. Before anything is stored it's scrubbed: seed phrases, private keys and the like are rejected outright, addresses are masked, and exact amounts are coarsened to buckets ("a small amount"). And if you never opt in, nothing is written at all.
#Turning it on
Memory has two scopes you control independently:
| Scope | Covers |
|---|---|
| defi | the main Sup agent and Telegram |
| trade | the Strategy Studio / trading agent |
Enable memory (and either scope) from the agent's memory settings. You can also switch off passive capture so the agent only remembers when you explicitly ask it to. Anything stored can be listed, exported, or deleted per scope.
#Your data, your control
- Scoped to you — every memory is stored under your own user key and is only ever read back for your chats.
- Deletable — remove one memory or wipe a whole scope, whenever you want.
- Off means off — with memory disabled the agent behaves exactly as before: no recall, no writes, no change to its answers.
#Developer note
Memory is built in — no external memory service — and activates only when both gates are on: the operator flag SUP_MEMORY_ENABLED and the per-user opt-in. Otherwise a no-op null provider is used and the prompt is byte-for-byte unchanged. The app codes against a MemoryProvider interface; writes pass through server-side redaction, and recall is a hybrid of vector + keyword search over our own store, capped by SUP_MEMORY_INJECT_LIMIT. Per-user control is GET / POST / DELETE /api/agent/memory. See Sup Agent.
