How it works

From workflow design to verified execution

Design

Build workflows in the visual designer. Compose reusable sub-workflows, attach instruction files with your coding guidelines, add decision branches and approval gates — and keep your own in a personal library that travels across projects.

Connect

Add one entry to your agent's MCP configuration pointing at the engine's streamable HTTP endpoint. Claude Code, Codex and any MCP client connect the same way.

Execute

The agent calls ccw_start and follows the steps the engine hands it. Step order is enforced, shell output is hash-verified, and approval gates halt until a human decides.

Observe

Observe long-running deterministic tasks as they execute. With the engine enforcing every step, even smaller LLMs perform like powerful large models.

Install & run

Self-hosted in three steps

1
Download. Get the engine zip and your license key from your account page. The free Starter tier includes both.
2
Configure. Unzip, install the runtime dependency, copy config.example.json to config.json and paste in your license key. The engine refuses to start without one.
3
Run. Start the API server for the web GUI and dashboard at localhost:3001, and the MCP server for your coding agent on port 3002.

Requires Node.js 22 — the engine ships as precompiled bytecode built for that runtime. Activation is offline; nothing phones home.

Go to your account

unzip codycody-engine-v1.0.0.zip
cd codycody-engine
npm install

cp config.example.json config.json
# paste your license key into config.json

npm run start:api   # web GUI + API on :3001
npm run start:mcp   # MCP server on :3002

Connect

One config entry, any agent

Register the engine as an MCP server and your agent immediately sees the execution tools. The engine serves streamable HTTP on your machine — every MCP client connects with the same entry.

The agent authenticates with an agent token: create one on the Agent Tokens page in the engine's web GUI (the secret is shown once) and pass it as the Authorization header. Tokens are long-lived and revocable per agent, so a coding agent or CI job runs for as long as you allow — separate from your browser session.

{
  "mcpServers": {
    "workflow": {
      "type": "http",
      "url": "http://127.0.0.1:3002/mcp",
      "headers": {
        "Authorization": "Bearer wsk_...your agent token..."
      }
    }
  }
}

Packages

What's in a workflow package

Workflows & sub-workflows

Complete, tested processes for a job — review, release, bug fix — composed from reusable sub-workflows.

Instruction files

The guidance injected into each step: review checklists, coding standards, verification rules.

Drop-in ready

Import into your engine, adjust the variables, run. Package updates are included with your purchase.

FAQ

Questions, answered

Which coding agents work with CodyCody?: Any MCP-compatible client: Claude Code, Codex, or your own agent. The engine exposes execution tools over streamable HTTP.
Is it self-hosted, and does it phone home?: Self-hosted, and no. You run the engine on your own machine or server; license activation is offline via a signed key, so it works fully air-gapped. Your code and data never pass through us.
What is a personal profile — and what's a seat?: Each user signs in and gets a personal profile: their own library of workflows and skills that follows them across every project, bound to your instance. A seat is one such profile. The free Starter tier includes one; Pro is priced per profile.
How do coding agents and CI authenticate?: Long-lived, revocable agent tokens issued from your account — separate from the browser session, so a CI job or agent runs for as long as you allow and can be revoked on its own without affecting anyone else.
What does the license cover?: The engine is licensed per profile, per year, updates included. Starter is free for one profile; Pro is per seat; Team adds a client-reuse license for agencies; Enterprise adds SSO, a site license and a signed key for air-gapped use. Workflow packages are one-time purchases with updates.
What is a workflow package?: A ready-made set of workflows, sub-workflows and instruction files for a specific job — code review, a release pipeline, a migration, a security suite. Drop it in and run it. Start with the free Code Review package.
Can I get a refund?: Yes — 14 days, no questions asked. See our refund policy.

See pricing