Built-in memory
Best for concise user preferences and recurring workflow hints.
Comparison
Built-in memory is useful for concise preferences and stable project guidance. remem is for engineering memory that must be searchable, auditable, project-scoped, and recoverable.
Use cases
Keep required team guidance in checked-in docs. Use built-in memory for stable preferences. Use remem when the evidence trail matters.
Best for concise user preferences and recurring workflow hints.
Checked-in project conventions and team guidance loaded by the host.
Best for decisions, bug-fix rationale, timelines, and project history.
Best when you need to inspect why a memory was injected.
What remem adds
remem complements built-in memory by keeping a structured local memory store that agents and tools can query.
Find historical decisions and root causes by query.
Inspect why memory was visible or injected.
Keep project memory in a local SQLite/SQLCipher store.
Expose memory to coding agents and local tooling.
Native memory
Its official memory guide distinguishes project instructions from auto memory. Both can carry context across sessions. Automatic persistence alone is not a reason to add another memory system.
Keep concise project conventions and preferences in the host's instruction and memory files.
Add remem when you need queryable project decisions, raw evidence, staleness labels, review queues, or injection audits from its local store.
Search for one earlier decision, open its source, and check its project and branch before relying on it. Follow the Codex verification walkthrough or Claude Code setup.
Install
Start with the host you use most, then add the other host later with `remem install --target all`.
brew install majiayu000/tap/remem
remem install --target codex
remem doctor
remem search "root cause"