Flow v5.0.0

Your to-do list has two items.

  1. Say what you want. to do
  2. Merge. to do

Everything else is Flow's list. A coding agent takes the task, builds it on a branch and opens a PR. GitHub Actions gates it, then QA, code-review and security reviewers read it, each in a fresh session.

Set up Flow: getflow.now/start

Tell your agent this line. Open source, Apache‑2.0.

flow · Replayed from PR #136 in Flow's own repo, shortened, with today's check names. Your first line is illustrative.

1You ask.

In plain words, or open a GitHub issue and let Triage draft the task. Approving the task is your first approval.

task-writerwrote the task flow-0100 in .flow/tasks
criteria  8, each one checkable
1  A 789,000-byte diff is not cut when the limit is set to 900,000
2  With no setting, the limit stays at 300,000
4  An invalid or too-large value fails loudly, naming the setting
touches  the files it declares; CI refuses a diff outside them
mainflow-0100 ready

2You start it.optional

Say it in a fresh session, or let Flow start a Claude Code routine on it.

routineWork the next ready task.
mainflow-0100  in progress
githubPR #136  [flow-0100] A repo sets its review diff limit in config.yml

3You wait.nothing to do

If the agent hits a decision that is yours, it stops, marks the task blocked and writes down the question. A failure goes back to the agent, not to you.

Checks on PR #136All checks have passed · 6 successful, 1 skipped
  1. flow-gates/gate build, lint, test, coveragepassed
  2. flow-gates/source-roots-plan scope check, flow-doctorpassed
  3. flow-gates/source-root already covered by the gateskipped
  4. flow-review/qa starts once the gate passespassed
  5. flow-review/code-reviewpassed
  6. flow-review/securitypassed
  7. flow-status/sync-status task moved to in reviewpassed
flow-review/qaapproved
All 8 acceptance criteria have a proving test that asserts the actual outcome, not just that nothing threw. I re-ran the suite with no ambient environment variables: 65/65 pass.
flow-review/code-reviewapproved
The precedence is implemented as specified, and the ceiling applies to all three sources. A bad value fails loudly, naming the key.
flow-review/securityapproved
No High or Critical findings. I checked that a PR can't raise its own limit: the reviewer reads the base branch's config, not the PR's.

4You merge.

Read the PR. Every criterion is ticked next to the test that proves it. That is your second approval.

PR #1368 of 8 criteria proved · 65/65 in flow-review.test.mjs · 1,448 in the full suite
1 A 789,000-byte diff is not cut when the limit is set to 900,000
2 With no setting, the limit stays at 300,000
4 An invalid or too-large value fails loudly, naming the setting
criteria 3 and 5–8 proved the same way, each next to its test
mainflow-0100 done

Bring your own agent.

Flow's rules live in one Markdown file in your repo. CLAUDE.md and AGENTS.md both point at it, so any coding agent that reads them can take a task and follow the same loop.

The builder never grades its own work. Every review runs in a fresh session that never saw the code being written.

The runners that work unattended (the worker routine, triage, review) run on Claude Code today, and stay off until you switch them on. All the runners

Who does what in Flow
BuildsClaude Code, Codex, Cursor, you, or any agent that reads AGENTS.md
GateGitHub ActionsThe same checks for everyone. The trust lives in CI, not in which model you picked.
ReviewsQA, code review, securitySonnet for QA, Opus for code review and security, each in a fresh session. Every summary names the model that answered.
MergesYou

From an issue to a PR.

Spot a bug on your phone and write one sentence in a GitHub issue. What comes back is a pull request to review, not a ticket number.

With automation on, Triage reads new issues each weekday morning and posts a draft task as a comment, labelled proposed. Change the label to approved and the next sweep makes it a ready task, and Flow starts a worker on it. Without automation, tell your agent Triage issue #12 with task-writer.

Triage only listens to people who can already direct the repo. The recipe

Issue #91 in Flow's own repo, shortened

  1. 30 SepgithubIssue #91: a task picked up again could get stuck in progress.
  2. 30 Septask-writerWrote task flow-0104 from it, with 8 criteria.
  3. 30 SepyouApproved the task. flow-0104 ready
  4. 1 OctagentBuilt it on a branch and opened PR #156.
  5. 1 OctgithubThe gate and the reviewers ran on the PR.
  6. 2 OctyouMerged. flow-0104 done

Failures became rules.

Flow built itself through its own gate. The things that went wrong are now checks.

183tasks through its own gate
2,200+tests
97%line coverage

Flow's own repo, as of v5.0.

  1. brokeA parse error in an unchecked folder silently dropped messages for a week.now: CI refuses any source folder it can't check
  2. brokeAn agent finished, then never opened the PR.now: a workflow opens the PR
  3. brokeTwo AI reviewers passed an oversized diff they hadn't fully read.now: if a reviewer can't see the whole diff, the check fails
  4. brokeReviewers ran, and were billed, on pushes the gate had already failed.now: the reviewers start only after the gate passes

Who it fits

Solo builders and small teams with several projects, on GitHub Actions. It is early: there is no hosted UI, and it works best with small, well-scoped tasks. Tasks are Markdown files in your repo.

Add it to your list.

Tell your agent this line. Claude Code, Codex, Cursor, any agent that can read a web page. Pinned to v5.0.0; it usually asks for two GitHub settings.

Set up Flow: getflow.now/start