Project Os For Codex

🚦 Project OS for Codex

The open-source control plane for Codex projects: visible progress, resumable context, safe handoffs, and reusable knowledge.

Independent open-source project. Not affiliated with or endorsed by OpenAI.

Built for Codex. Connect through MCP, keep project truth in Git, and make every handoff resumable.

🚀 Quick Start · 🤖 Connect Codex · 🧭 Features · 📦 Deployment · 🔌 Interfaces

Project OS for Codex is for the moment when a team asks: What is the AI doing? Where should the next session start? How can another person or AI take over without rereading every chat?

It is not another AI chat window. It is the control plane around the work: kickoff card, acceptance criteria, current progress, Git evidence, next action, reusable knowledge, and a handoff package that both humans and agents can read.

💡 Why Does This Exist?

AI can generate code quickly, but real projects still fail in very ordinary ways:

• The project progress is hidden inside chat history.
• The next AI session does not know where to start.
• Humans cannot tell which tasks are done, blocked, risky, or waiting for review.
• Handoffs become painful because context is scattered across prompts, screenshots, commits, and private notes.
• Teams lose trust because there is no visible project trail.

Project OS for Codex turns those scattered pieces into one workspace: project goals, acceptance criteria, Git records, progress events, risks, next steps, knowledge, and handoff packages.

Built from repeated real delivery work

This is not a weekend concept built from imagined agent problems. It was distilled from recurring problems seen across many real internal and client projects, then refined through sustained Codex use: context loss, invisible progress, unclear acceptance, difficult handoffs, and knowledge that disappears after delivery.

The anonymized July 2026 maintainer snapshot below shows 14,570 Codex tasks, 8.8B lifetime tokens, a 23-day streak, and 743 skill uses. These numbers are evidence of maintainer practice—not repository users, downloads, adoption, or 14,570 separate projects.

Explain It Like I Am New

Think of this system as a project cockpit for AI-assisted development.

When an AI helps you build a project, it should not only write code. It should also leave behind:

• what it changed;
• why it changed it;
• what still needs to be done;
• what risks remain;
• what the next human or AI should read first.

This repository provides the structure for that cockpit. It helps a project become something another person or AI can continue, instead of a one-time chat transcript.

Connect Codex

Do not give an AI your website username and password. From a project page, create a short-lived AI credential that is bound to one workspace and one project, then run the generated MCP command in your own terminal.

The first production-oriented slice exposes two real MCP tools:

• project_os_get_context — reads the kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step;
• project_os_append_progress — appends one validated, audited, idempotent progress event, an agent-reported verification note, and one matching project-record Git commit.

Credentials expire after 24 hours or 7 days, can be revoked independently, are stored only as hashes, and cannot access members, keys, deletion, publication, or deployment.