OpenFlows Documentation
OpenFlows is a self-hosted orchestration layer for running autonomous AI development teams on top of Coder. Read these docs to install, operate, extend, and contribute to the system.
Getting Started
Install OpenFlows, obtain tokens, and run your first autonomous issue-to-merge cycle.
Quick Start
The 10-minute path from clone to a working OpenFlows stack.
Installation
Docker Compose, bootstrap, tenant creation, and verification.
Token Guide
GitHub OAuth, Coder external auth, and session tokens.
First Issue Walkthrough
What happens when you create a GitHub issue and the agents take over.
Core Concepts
The ideas that make OpenFlows work: architecture-first orchestration, the agent team, and the Coder integration model.
Architecture-First Development
Why OpenFlows plans before it executes and why that matters.
The Agent Team
NEXUS, FORGE, SENTINEL, VESSEL, and LORE - roles, boundaries, and handoffs.
PocketFlow & SharedStore
The flow graph, typed state contracts, and the Node lifecycle.
Coder Integration
How OpenFlows runs on top of Coder and why the split is intentional.
Security Model
Identity, audit, secrets, and workspace isolation.
Architecture
Detailed design of the orchestration engine, state machine, recovery systems, and agent lifecycle.
System Design
Components, data flow, SharedStore schema, and crash recovery.
Agent Roles
Per-agent responsibilities, permissions, and workspace behavior.
Workspace Lifecycle
Provisioning, execution, teardown, and per-evaluation isolation.
State Machine & Recovery
NEXUS reconcile, failure detection, and self-healing.
Decision & Routing
How agents make decisions and how work is routed between them.
Guides
Practical instructions for configuring, extending, and operating OpenFlows in production.
Agent Setup
registry.json, model routing, CLI modules, and worker scaling.
Model Routing
Provider selection, cost optimization, and adversarial review.
Multi-Tenancy
Running multiple teams on a single Coder deployment.
Extending OpenFlows
Skills, MCP servers, and custom models without code changes.
Operations & Monitoring
Logs, TUI, metrics, and production runbooks.
Troubleshooting
Common failures, diagnostics, and fixes.
Reference
Exact specifications for configuration, APIs, and command-line usage.
API Reference
REST endpoints, control-plane APIs, and integration points.
registry.json Schema
Complete field reference for agent configuration.
Environment Variables
Every env variable OpenFlows reads at runtime.
CLI Commands
openflows bootstrap, tenant, and development commands.
Contributing
How to build, extend, and test OpenFlows as a contributor.
What OpenFlows is not
Not a CI/CD platform
It orchestrates agents and integrates with your existing CI/CD pipeline; it does not replace it.
Not a SaaS offering
It is self-hosted on your infrastructure. You retain full control over data, models, and execution.
Not an IDE
It works with any editor through Coder workspaces. It orchestrates agents, not your editor.
Not a code generator
It coordinates agents that write code. The value is in the architecture, contracts, and review gates.