Steer, build, and accept stay distinct.
An agent working inside a code branch cannot quietly weaken a test or rewrite its own requirements to make a build pass. Defining the goal, writing the code, and accepting the result are separated by design.
The Operating Agreement for AI-Assisted Teams
Let AI write the code.
Keep engineering judgment, risk boundaries, and acceptance yours.
Fast code generation is only a win if your team still knows what shipped and why it is safe. AgentFlow 2.0 gives AI-assisted engineering teams a clear operating model: the agent that writes the code never approves the release, ceremony scales with risk, and recurring mistakes turn into shared team rules.
Open source (Apache-2.0) · Works with Claude Code, Codex, Gemini CLI, Grok, and OpenRig · Scales from one developer CLI to a full team squad
One slice. Proportional ceremony by risk.Click a scenario to see how governance adapts
Test criteria are locked up front. Low-risk work completes in a single builder pass without unnecessary bureaucracy.
Routine slice: automated test and file-boundary checks run first; no heavyweight review panel required.
Why care · What it brings to the table
Built for VP Engineering, CTOs, tech leads, and developers who want the speed of agentic coding without losing accountability over their codebase.
An agent working inside a code branch cannot quietly weaken a test or rewrite its own requirements to make a build pass. Defining the goal, writing the code, and accepting the result are separated by design.
A simple UI or docs update finishes in a single pass. The moment a change touches authentication, billing, migrations, or security rules, AgentFlow automatically escalates to independent cross-model review.
When an agent gets stuck in a rework loop or hits a boundary violation, AgentFlow captures the pattern and proposes a clear, human-reviewed update to your repository's engineering rules.
Built with AgentFlow
AwesomeAwesomeness was built across multiple sessions using AgentFlow's role boundaries, automated evidence checks, and human acceptance gates. Both the live application and its complete delivery history are public to inspect.
Adopt at your own pace
You don't need a complex multi-agent cluster to start. AgentFlow uses the coding tools already installed on your machine and grows with your team.
See the 3-step setup →Run AgentFlow with a single tool (Claude Code, Codex, Gemini CLI, or Grok) to keep your requirements, test criteria, and release checks structured.
Have two coding CLIs installed? Let one model family build the feature and a different model family review the diff—catching blind spots before you review.
Coordinate dedicated architecture, building, QA, and review seats working across isolated Git branches with shared governance.
Where it fits in the ecosystem
AgentFlow SDLC 2.0 works completely standalone, and connects cleanly with the rest of our open-source systems when you want parallel sandboxes, live telemetry, or personal context.
AgentFlow defines the scope, risk tier, and acceptance criteria; Meshloop executes the build tasks in parallel isolated Git worktrees.
Watch live agent behavior in Grafana or Datadog with agent-otel-bridge, and analyze session time, rework loops, and cost afterward with Dendro.
Link repositories to Holoself so agents inherit your approved architectural standards and working preferences automatically.
Start small. Scale with confidence.
Built by Samuel Mota · Move the Needle
Open source · Apache-2.0 · Release 2.0
Let AI write the code while keeping engineering judgment, risk boundaries, and release acceptance explicitly human-owned.
When code generation becomes cheap, decision quality and clear ownership become the bottleneck. AgentFlow keeps roles, risk boundaries, and release sign-off in your team's hands.
Separates steering, building, and independent acceptance across risk-calibrated slices, turning recurring review friction into human-approved engineering rules.