Project memory
A bank is the boundary Remember uses to store, retrieve, and summarize memories. The default is one bank per project. Codex and Claude Code can read the same project bank without needing to share their own chat histories.
Project banks
| Situation | Default behavior |
|---|---|
| A new session in the same checkout | Uses the same project bank. |
| A linked Git worktree | Resolves the main checkout and uses its bank. |
| Switching from Codex to Claude Code | Uses the same bank when opened in the same project, if both integrations are installed. |
| Two unrelated checkout paths with the same repository name | Uses different banks. |
| An explicit path or bank mapping | Uses the configured scope. Only share a bank across repositories intentionally. |
Remember combines the repository name with a stable hash of its canonical main checkout path. A separate clone is not a linked worktree and can get a different bank. See configuration before overriding this isolation.
What gets captured
The agent hooks capture eligible conversation turns and queue them for retention. The local worker processes queued writes. Original text can support recall alongside extracted facts, and Pages can summarize what a bank has learned. Depending on settings, Remember can also seed a bank from Git and use repository surveys. Capturing a turn does not make every inference from that turn correct.
retainSessions: false stops automatic transcript retention. It does not stop recall, memory tools, or separately configured Git ingestion. Use project opt-in or disable the integration when you need a wider boundary.
Where it lives
The daemon listens on 127.0.0.1. By default, agent configuration and daemon state live in ~/.remember. The Pg0 database is separate at ~/.pg0/instances/remember-embed-coding-agent, so changing REMEMBER_HOME alone does not move it. The local database can persist across daemon restarts.
The process that reasons over memory can be local or hosted. Configure that choice explicitly.