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.
Connect
Add one entry to your agent's MCP configuration — stdio for local, streamable HTTP for a shared server. Claude Code, Codex and any MCP client connect the same way.
Execute
The agent calls instance_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
Watch instances live, inspect per-step logs, query weekly metrics — and let the agent debug its own failed runs with the same tools.
Connect
One config entry, any agent
Register the engine as an MCP server and your agent immediately sees the execution tools. Local over stdio, or shared over streamable HTTP with bearer-token auth for the whole team.
{
"mcpServers": {
"workflow": {
"command": "node",
"args": ["./dist/mcp-server.js"]
}
}
}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 stdio or streamable HTTP.
- Is it self-hosted?
- Yes. You run the engine on your own machine or server. Your code and data never pass through us.
- What is a workflow package?
- A ready-made set of workflows, sub-workflows and instruction files for a specific job — for example a code-review pipeline or a release process. Drop it in and run it.
- What does the license cover?
- The engine license is per organisation, per year, including updates. Workflow packages are one-time purchases and include updates to that package.
- Can I get a refund?
- Yes — 14 days, no questions asked. See our refund policy.