project-os-for-codex

About

Project OS for Codex exists because handing a coding agent a long-running project usually means sharing passwords, losing context between sessions, and having no auditable record of what the agent actually did. It provides a web dashboard plus a strict two-tool MCP server: one tool returns the current kickoff card, acceptance criteria, and handoff package, and the other appends one validated, idempotent progress event with an agent-reported verification note and a matching commit in a separate record repository. A fail-closed preflight verifies the credential, project binding, and exact tool surface before Codex starts, and high-risk operations like key management or deployment are deliberately kept outside the MCP surface for humans. Handoffs use short-lived, scope-limited credentials — 24-hour or 7-day expiry — instead of shared passwords, with everything hashed and independently revocable. Solo developers running Codex on multi-session projects use it to keep work auditable and handoff-safe.