Download Latest Version flow-next v3.15.1 source code.zip (16.8 MB)
Email in envelope

Get an email when there's a new version of Flow-Next

Home / flow-next-v3.13.3
Name Modified Size InfoDownloads / Week
Parent folder
flow-next v3.13.3 source code.tar.gz 2026-08-02 13.7 MB
flow-next v3.13.3 source code.zip 2026-08-02 16.4 MB
README.md 2026-08-02 1.6 kB
Totals: 3 Items   30.1 MB 0

Run Codex from more than one home and flow-next can now live in all of them. Plus review loops get twice the room before they stop and ask you to look.

Changed

  • Codex installs now honor CODEX_HOME. Run CODEX_HOME="$HOME/.codex-work" ./scripts/install-codex.sh once for each alternate Codex home; generated skills and agents now resolve their bundled tools from that same home at runtime. Installer progress and cleanup messages name the real destination, while an unset CODEX_HOME keeps the existing ~/.codex behavior.

  • Review loops get twice the room before they stop and ask for you. MAX_REVIEW_ITERATIONS defaults to 8 instead of 4. The cap counts review dispatches, which cannot tell a loop that is genuinely stuck from one that is converging while each fix surfaces one more small thing. In a single session three specs hit the cap at 4, and every time the findings left were trivial residue - two were reset by hand and shipped almost immediately after, one on the very next round. Eight buys room for that pattern without removing the stop the counter exists for: it still refuses to dispatch at the cap, still exits 4 with ESCALATE:, and still resets only on a SHIP verdict or an explicit flowctl spec reset-review-rounds. Set MAX_REVIEW_ITERATIONS yourself to go higher or lower; it can never be zero or disabled. This is an interim measure - the real fix is a convergence-aware terminal that reads the severity trend and can escalate to a human on purpose, rather than a bigger number.

Source: README.md, updated 2026-08-02