Build local shared memory when you work across projects and AI tools.
Last reviewed:
⌕
Search runs on this device.
On this page
Overview
This system is for developers who move between Codex, Claude Code, or Gemini CLI and want projects and approved decisions in one local memory. If you need automatic cloud sharing of private content, this local-first model is not the right fit.
What problem does it solve?
When several tools work on one project, decisions and work status can become scattered. The system maintains approved working memory in a shared local layer; it does not replace coding tools or provide a cloud collaboration service.
Data and permissions
You select the sources. Local storage does not make every file safe: review exports before transfer and do not publish credentials, private text, or sensitive paths. Information without evidence must not become a verified fact.
What to expect from measurements
actual uses verifiable data; estimated is a forecast; unavailable means required data or pricing is missing. Costs use a confirmed price book. Missing values are not zero, and a cost comparison alone does not establish savings caused by the system.
Completion checklist
Before continuing, identify the tools you use, which projects are genuinely shared, and which information may be transferred. If you only need measurement views, read the Dashboard-only limitations. For shared memory, continue with environment preparation and the Obsidian decision.
With analytics consent, your answer helps us choose and improve guides.
Help improve these guides
With your permission, views, clicks, copies, article-end visibility, feedback and broad search topics are stored as daily counts in the project’s Neon database to plan better guides. This analytics payload excludes search text, URL parameters and visitor identifiers. Hosting infrastructure processes network information when receiving requests. Your choice stays in this browser. Revoking consent stops future events, but existing aggregate counts remain.