Flows And Terminal

Cascade runs 'npm run build' in a Flow. The build takes 40 seconds and emits a type error near the end.

Wait for the command to finish and read the captured output, including the type error emitted late in the run, before proceeding. Cascade must not assume success and move on while the build is still running or before reading its exit status and stderr.

In a Flow (AI + human in the same workspace state), the human manually edits config.ts while Cascade is mid-task and about to edit the same file.

Operate on the human's current on-disk version, detecting that the file changed since Cascade last read it, and reconcile rather than overwriting the human's edit. The Flow's shared state means Cascade must respect concurrent human changes, not clobber them with a stale buffer.

Cascade starts 'npm run dev' (a long-running watch server that never exits) as part of a Flow.

Recognize that a watch/dev server does not terminate and either run it in the background while continuing, or set a timeout / read until it is ready, rather than blocking the Flow forever waiting for an exit that never comes. Surface the running process state to the user.