About OpenFlows
OpenFlows coordinates five specialized AI agents through a Redis-backed state machine to take GitHub issues all the way to merged, documented pull requests. GitHub identity is brokered by Manager through a GitHub App installation. The pipeline can run autonomously - you wake up to completed features, reviewed PRs, and updated documentation.
The team
Syncs GitHub issues, assigns work to agents, and coordinates the tenant pipeline. Manager provisions and manages the workspaces.
Receives tickets, writes PLAN.md, implements code segment by segment, and opens pull requests.
Reviews every code segment against 5 criteria: correctness, security, test coverage, standards compliance, and no regressions.
Handles CI status, resolves merge conflicts, and squash-merges approved PRs after SENTINEL approval.
Writes ADRs (Architecture Decision Records) and updates CHANGELOG.md after each successful merge.
"Coder governs where agents run. OpenFlows governs how they coordinate. Code is the output. Architecture is the product."
How it works
NEXUS polls GitHub for open issues, while Manager provisions tenant workspaces. FORGE receives the ticket, writes a PLAN.md, and implements the code segment by segment. SENTINEL reviews every segment against five criteria before approval. VESSEL handles CI status and merges approved PRs. LORE documents everything with ADRs and CHANGELOG updates.
The entire pipeline runs without human intervention. NEXUS only reaches out when it genuinely needs you - spec ambiguity, security concerns, or resource limits. Otherwise, the team runs autonomously within your governed environment.
What we stand for
NEXUS coordinates tickets and agents, while Manager provisions workspaces and brokers runtime credentials. The pipeline escalates decisions that require a person.
Each agent has a role, skills, hooks, and a workspace runtime identity. Manager brokers short-lived GitHub App installation tokens scoped to the tenant repository; human GitHub OAuth remains separate.
Manager persists operations and uses leases so another instance can resume queued work. Agent coordination and workspace reconciliation provide additional recovery paths.
Each agent's LLM provider and model are configured independently in registry.json. FORGE and SENTINEL can use different providers - Anthropic for the builder, OpenAI for the reviewer - so the reviewer's blind spots differ from the writer's. SENTINEL spawns fresh per evaluation, read-only and bias-free.
The orchestration engine - PocketFlow core, SharedStore, agent harnesses, and TUI setup wizard - is on GitHub under the MIT license. Install via npm, cargo, Docker, or a one-line curl installer. Self-hosted on your infrastructure, with Coder AI Gateway and LiteLLM fallback for any model provider.
FORGE implements and opens PRs in 15–30 minutes. SENTINEL reviews every segment automatically. VESSEL merges when CI is green. A 2-person startup can ship 40 features in a month because the pipeline eliminates the PR review queue and founder context-switching.
When VESSEL detects a merge conflict, it does not create a new branch or lose context. It writes CONFLICT_RESOLUTION.md and re-routes the ticket back to the same FORGE worker. FORGE reworks the implementation, re-commits, and VESSEL re-monitors CI - no manual rebase.
LORE writes Architecture Decision Records and updates CHANGELOG.md after every successful merge. Technical decisions are captured automatically, not as an afterthought. The team ships code and the paper trail writes itself.
Community
OpenFlows is an MIT-licensed, self-hosted AI software team that turns GitHub issues into reviewed, production-ready pull requests inside your Coder environment. Contributions shape the agents, NEXUS orchestration, FORGE implementation, SENTINEL adversarial review, VESSEL merge automation, LORE docs, through skills, MCP servers, new model integrations, and the PocketFlow flow graph.
Maintained by the AgenticFlow team. Whether you're hardening the planning gate and failure recovery, tuning agent personas and permissions, or documenting architecture, your work directly shapes how autonomous development teams operate.
