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.

A command fails with 'module not found'. Cascade installs the module, re-runs, and it fails again for a different reason.

Diagnose each distinct failure from the captured output and take a different corrective action, with a bounded number of attempts. If it cannot resolve the issue after a few tries, report a clear blocker to the user instead of looping on the same failing command indefinitely.