Run it yourself.
CMOS is free to install from npm and needs Node 20+. Follow the guide to set up a project and open your first session.
Read the guideCMOS
Pick up where the work left off.
Every new agent session starts cold. CMOS keeps what your project decided and why, and what’s still open, in a SQLite database in your repository, and brings it into the next session.
Free on npm · v3.5.0
The reasoning is what gets lost.
A diff shows what changed. It doesn’t show what was tried first, what was decided and why, or what’s still open. That’s what the next session needs, whether the next session is an agent or a person.
How it works
-
Record a decision and its reason.
You make the decisions. Your agent writes each one down with the reason, as it works.
-
Start the next session with it.
In Claude Code and Codex, the CMOS plugin brings the record into each new session on its own. Without the plugin, one call to
cmos_reviewreturns the same digest. -
Add planning when the project needs it.
A new project starts as a Ledger of decisions and what you learned. Planner adds next steps. Builder adds sprints and missions with objectives and success criteria, and starting a mission brings up the past decisions that bear on it.
Local first. The dashboard is optional.
The core loop runs with no network connection, and everything lives in your project’s SQLite database. Nothing needs an account. An optional one at cmos.aquex.ai keeps a hosted copy of the whole database, uploaded a few minutes after your agents stop writing, and gives your projects addresses so they can message each other. One setting turns the uploads off.
We build this site with it.
Every mission, decision and learning behind aquex.ai lives in CMOS, including the ones behind this page.
Two ways to start
Or learn it with us.
AI Workshops & Training: a shared way of working with AI, with context and decisions that carry between people and sessions. Half a day to several weeks.
Talk to usCMOS keeps what your team and your agents write down. It can’t tell you whether a decision was right. It snapshots the database before a restore, before and after a sprint closes, and before pruning snapshots. Back it up yourself before other destructive operations.