Skip to content

Great Cto

You already have the agent. This is everything around it. great_cto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the…

Install

$npx great-cto init
Claude Code
claude mcp add great-cto -- npx great-cto init
Cursor / Claude Desktop (mcp.json)
{
  "mcpServers": {
    "great-cto": {
      "command": "npx",
      "args": [
        "great-cto",
        "init"
      ]
    }
  }
}

Install command taken from the project's README or registry entry. Always review code before running it.

Ship products with the coding agent you already have.

npx great-cto init

Website · One real run → · Blog · Changelog

Русский · 简体中文 · 繁體中文 · 日本語 · 한국어 · Español · Português · Deutsch · Français


Your coding agent ships code. This is what checks it.

Describe a product or a feature. 72 agents with narrow jobs take it through brief, architecture, build, review and security; a second model from another family reads the same diff. Three decisions stay yours — what gets built, how, and whether it ships — and what lands is a repository you own and a URL that works. You pay your own LLM provider; great_cto is MIT and bills nothing.

Quick start

npx great-cto init

Restart Claude Code. Day to day there are three things:

In Claude Code In the terminal
Start work /start "add Google login" great-cto run "add Google login"
See what needs you /inbox great-cto status
Continue /resume great-cto resume

/start takes a new product or a task in an existing project and picks the workflow itself. /resume continues only what you already approved; a pending decision still waits for you. Everything else — /review, /spec, /save, /digest and the rest — is there when you need it: all commands.

The board at localhost:3141 opens on Work — your tasks, the decisions waiting on you, and what already shipped. Cost, agents and reviewers are under Tools. Nothing on it renders an absence as a pass: a check that could not decide reads unverifiable, a cost nobody measured unmeasured, a reviewer that could not run unavailable.

On OpenAI Codex

npx great-cto init --host codex gives Codex the skills, the MCP server and six safety guards as plugin hooks (approve them once: run codex in a terminal and choose Trust all and continue). Codex has no native plugin surface for slash commands or role agents, so the pipeline runs through the CLI instead:

great-cto run "add Google login" --host codex --allow src,tests,docs
great-cto status --host codex
great-cto resume --host codex

Plugin refresh is explicit by default (great-cto upgrade codex). On macOS, sh scripts/codex-auto-update.sh enable opts into a six-hour per-user timer; status inspects it and disable removes it. Each tick validates the Git marketplace origin before asking Codex to upgrade. It follows the configured Git ref, not npm releases, and changed hooks still need host review in a new session. Details, mixed runs and Codex as the second reviewer: Codex host guide.

When it stops you

One line in .great_cto/PROJECT.md:

approval-level Stops you at Stops
ship-only the deploy — and briefs you on what gets built 1
product-only what we build · whether it ships 2
gates-only (default) what we build · the design · the deploy 3
strict the design · code review · the deploy 3
auto nothing in the pipeline 0

Similar plugs

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…

Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…

Explore related