SuperchargeMemory
Curated notes versus experimental memory commands
Memory
Two stores exist. Do not mix them up.
Curated notes (on by default)
The agent keeps short notes it can add, replace, and remove in one call. Files:
| File | Who it describes | Cap |
|---|---|---|
~/.supercharge/memories/USER.md | You. Shared across bots, because there is one user. | 1375 characters |
~/.supercharge/memories/MEMORY.md | This bot's environment and conventions. | 2200 characters |
SUPERCHARGE_HOME changes the parent. Entries are separated with §. The cap is checked on the final list. Notes that look like prompt injection are rejected. If a file is free-form and not the entry format, it is not overwritten. A .md.bak is kept.
These notes are inserted into the system prompt the next time that prompt is built, on a binary that includes the feature. They are not the experimental topic files.
In the prompt, /remember <text> saves a note immediately.
/remember the staging host is deploy.internalExperimental memory v2
Off unless you set SUPERCHARGE_MEMORY=1 or:
[memory]
enabled = trueThen these commands appear:
| Command | What it does |
|---|---|
/memory, /mem | Browse saved memories. /memory on and /memory off toggle the feature. /memory status shows queue and retention diagnostics in a v2 session. |
/flush | Summarize this session into memory now. Use it before /compact when you want the summary kept. |
/dream | Consolidate session logs into topics. |
/dream in upstream Grok depends on Grok's memory service. On this CLI, treat /dream as available only when your build and memory backend actually support it. If the command says it cannot run, use /flush and /remember instead.
Search across sessions uses the memory tool when that backend is enabled. Curated files stay the place for facts you want in every new prompt without turning v2 on.