About Coding OS

Hey — I’m Kourosh Ebrahimzadeh, a developer in Canada, and I build Coding OS. It is open source, Apache-2.0, and made by one person who got tired of explaining the same codebase to an AI agent every single morning.

The origin

Why This Exists

AI coding agents are genuinely good at writing code. What they are bad at is everything around it: remembering yesterday’s decision, knowing which file is the source of truth, noticing that a change breaks three callers, and stopping to think before editing.

So every session starts from zero. You re-explain the architecture, the agent re-discovers the same files, re-makes a decision you already rejected, and quietly re-introduces a bug you fixed last week. The model isn’t the bottleneck — the missing memory and the missing process are.

Coding OS is the layer that fills that gap. Not a smarter agent — a disciplined environment around the agent you already use.

The architecture

One Kernel, Three Brains

  • graph_os

    Indexes code, docs, and configs into a queryable graph, so an agent can ask who calls this and what breaks instead of guessing.

  • thinking_os

    Memory, learning, and metrics. Sessions record what they learned; the next one starts with a digest instead of amnesia.

  • board_os

    A Scrumban board with WIP limits, a definition of ready, and lifecycle hooks. Tasks are contracts, not vibes.

The long version — with the enforcement loop and the benchmark — lives on the landing page and in the docs.

Honest scope

What It Isn’t

Overclaiming is the fastest way to lose a developer’s trust, so here is the unglamorous half:

  • Not another AI coding agent. Coding OS sits on top of the agent you already pay for.
  • Not a model, a fine-tune, or a prompt pack. It is memory, structure, and enforcement around your agent.
  • Not a hosted service. It runs on your machine, in your repo, under your control.
  • Not finished. It is a young project, built in the open, and it will tell you when something is unsupported.

What actually runs today

Claude Code
full support.
Codex (CLI & app)
full support.
Humans
git hooks support.

If a runtime is not on that list, it is not supported yet — and you will not find it claimed anywhere else on this site.

Where it stands

The Road So Far

  1. Bootstrap

    Phase 0 · Shipped

    Architecture decisions, the ADRs, and a written product spec — before a line of the site existed.

  2. Launchable MVP

    Phase 1 · Shipped

    The site you are reading: synced docs, the community forum, the prompt catalog, and funding rails.

  3. Open UGC + content engine

    Phase 2 · In progress

    Community-submitted prompts with a real moderation queue, voting, and the blog engine behind it.

  4. Depth and scale

    Phase 3 · Demand-gated

    Deeper prompt tooling, search upgrades, and an in-app forum — each one waits for evidence that it is needed.

Writing

Notes From the Build

I write about what breaks, what the benchmarks actually showed, and the decisions I would make differently. Infrequent, and worth the wait more often than not.

Say hi

Reach Out

Bug reports, hard questions, and “this part of the docs is wrong” are all welcome — those are the messages that move the project. Pick whichever door is closest.

Coding OS is free and always will be. If it saves you time and you want to keep it going, supporting the project helps more than a star.