Introducing Coding OS

AI coding agents got fast. They did not get disciplined.

Anyone who has run an agent for more than an hour knows the failure modes: it dives into code with the wrong mental model, "finishes" something that doesn't run, forgets everything the previous session learned, and leaves no trace of why any decision was made. The models keep getting smarter, and the failures keep happening — because they aren't intelligence failures. They're process failures.

Coding OS is our answer: a cognitive operating system that installs on top of the agent you already use — Claude Code or Codex — and gives it what raw intelligence doesn't have: memory, structure, and discipline.

What it actually does

Run cos init in a repo and three layers come online, all served by one local MCP server:

• thinking_os — memory and method. Cross-session memory that survives context resets, a learning loop that turns failures into reusable patterns, and a complexity gate: before the agent may touch code, it must classify the problem (is this a known recipe, an analysis problem, or an experiment?) and record it. Thirty seconds of classification prevents hours of confidently wrong code.
• graph_os — structure. A precomputed knowledge graph of your codebase. Instead of grepping a symbol and opening fifteen files, the agent asks "who calls this?" and "what breaks if I change it?" and gets the real answer — including the dynamic-dispatch callers text search can't see.
• board_os — work state. A Scrumban board the agent itself operates: tasks with acceptance criteria, work logs that survive the session, WIP limits that stop it from juggling five half-done things.

Around those layers sits the part people usually notice first: hooks that enforce the process. A code edit with no traced spec gets blocked. A commit message that would corrupt the changelog gets blocked. A "done" without a passing verification gets blocked. Discipline an agent can rationalize away is discipline it doesn't have — so the important steps are impossible to skip.

Built on itself

Coding OS is developed under its own rules. The same gates that will block your agent block ours; every feature you get was dogfooded through the same board, the same hooks, the same verification matrix. "We use it ourselves" is easy to claim — the stronger claim is that our own development is blocked by the same machinery when we cut corners.

Get started

uv tool install coding-os
cos init

It's Apache-2.0 and free. The quickstart takes about five minutes; the docs cover the concepts and every adapter's exact enforcement surface — no overclaiming. If you get stuck, ask in the community forum; if you build a workflow worth sharing, we want to see it.

Agents don't need to be smarter to ship better software. They need an operating system.