| Name | Modified | Size | Downloads / 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. RunCODEX_HOME="$HOME/.codex-work" ./scripts/install-codex.shonce 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 unsetCODEX_HOMEkeeps the existing~/.codexbehavior. -
Review loops get twice the room before they stop and ask for you.
MAX_REVIEW_ITERATIONSdefaults 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 exits4withESCALATE:, and still resets only on aSHIPverdict or an explicitflowctl spec reset-review-rounds. SetMAX_REVIEW_ITERATIONSyourself 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.