ChangelogWaiting for the network turns on network capture

0.5.5

Released 1 November 2026.

A flow that waits for the network to go idle now turns network capture on by itself, the way a flow that stubs the network does. Before, such a flow run without --capture-net left the wait pending and still passed.

You can drop --capture-net from scripts that keep it only for waitFor: { networkIdle: true }. If you run with --strict-assert, a step left pending now fails the run.

CLI

  • Fixa flow with waitFor: { networkIdle: true }, directly or in a flow it runs, turns network capture on, and relaunches an app that is running without it
  • Fix--strict-assert (or config: { strictAssert: true }) fails the run when a step is left pending for lack of data, as well as when a step could not be performed

Agents & MCP

  • Fixrun_flow relaunches an app running without network capture when the flow waits for the network to go idle, and says so in its result