Persistent
State.
State survives across sessions.
A new way to manage your agentic engineering workflow.
Decapod is an application your coding agents call to keep engineering work aligned with your intent, within clear boundaries, and backed by evidence. Its agent-agnostic, daemonless metacognitive governance kernel works with Codex, Claude Code, Cursor, Antigravity, and other compatible agents. Each call returns a result and exits; task ownership, context, and exact-commit proof remain available across sessions.
cargo binstall decapod && decapod initOne initialization per project. No signup.
Now just tell your agent what you want.
SHOWCASE / DECAPOD AT WORK
Software is built in many domains. Decapod keeps agent work coordinated, bounded, and verifiable across them. Here are two very different applications.
01 / GAME DEVELOPMENT
Waystead is a procedurally generated, planet-scale survival RPG and dungeon crawler in active development. Its Godot codebase spans world generation, character systems, persistence, rendering, and delivery.
Decapod governs the coding agents working across those systems—preserving task ownership, context, boundaries, and evidence as the project evolves.
Use Decapod in your project
01 / 07 · IN DEVELOPMENT
Character creation, appearance, identity, and the start of a personal journey.
SHOWCASE / STARTUP SOFTWARE ENGINEERING
Agents can build the software behind an ambitious startup: features, infrastructure, identity, billing, and delivery. Decapod governs the work as teams and agents coordinate, review, and ship.
Parallel issue work, revalidation after upstream merges, and independent verification.
November 18, 2026 — three Ghostty terminals, three separate Antigravity CLI instances, each running its own Carbon/Hydrogen swarm.
FEATURES / THE GOVERNED WORKFLOW
State survives across sessions.
Authority stays bounded.
Evidence tied to exact commits.
Use different coding agents in one governed project.
THE GOVERNED WORKFLOW
Your coding agents call Decapod throughout the job. The application keeps decisions, ownership, boundaries, and validation evidence available across tools, engineers, and sessions.
Create, claim, prioritize, hand off, and complete work with an explicit owner and recorded outcome.
Task lifecycle 02 / CONSTITUTIONSensible defaults for agent decisions, backed by curated engineering golden paths, research, architecture, and software-business knowledge. Embedded in the kernel, agent-queryable, and open to community PRs.
Explore the Constitution 03 / INTENTKeep the original request and the agent’s interpretation in reviewable, versioned specifications.
Intent & decisions 04 / CONTEXTResolve the relevant rules and project context for a task, with traceable provenance.
Agent-first architecture 05 / WORKSPACESGive work its own branch and Git worktree, with optional container boundaries.
Workspace model 06 / CONCURRENCYCodex, Claude Code, Cursor, Antigravity, and other agents coordinate work in the same project through task claims, workspace custody, and handoffs—even across engineers.
Multi-agent workflows 07 / MEMORYKeep knowledge and work state available across sessions, agent tools, engineers, and handoffs.
Persistent context 08 / BOUNDARIESMake repository rules, ownership, and execution boundaries visible before work begins.
Bounded execution 09 / VALIDATIONRun required gates, inspect failures, repair supported problems, and revalidate.
Proof & validation 10 / EVIDENCETie validation evidence to the exact repository state and checks that produced it.
Proof contracts 11 / DELIVERYKeep publication blocked until required checks, authority, and evidence are satisfied.
Delivery workflow 12 / HISTORYPreserve the chain from intent and assumptions to work, decisions, receipts, and completion.
Artifact inventory 13 / RUNTIMEThe application runs when an agent calls it, then exits. Governance state remains available to the project.
Mental model 14 / INTERFACEKeep your coding agents. They call Decapod through CLI or structured RPC for decisions, boundary checks, and validation.
Agent APIOBSERVED AUTONOMOUS ENGINEERING
Watch the native Pi terminal as it calls Decapod, investigates a rejected check, repairs the code, and publishes the verified pull request.
Selected moments from one recorded Pi session. Tool calls play at original speed. On a phone, use landscape fullscreen for the largest text.
Bring your own agents.
Decapod governs their work.