Cascade Agent

User is in Cascade Chat mode and asks 'add a retry wrapper around the HTTP client'. Chat mode answers without editing, but the integration auto-applies the suggested code to disk.

Respect the mode boundary: in Chat mode Cascade explains/proposes but does NOT write files. To apply edits the user must be in Write mode (or explicitly switch). Surface the proposed diff and prompt the user to switch to Write mode rather than silently mutating the workspace from Chat mode.

User asks Cascade to 'rename the User.email field to User.contactEmail across the repo'. The change touches 14 files including a DB migration and tests.

Cascade produces a plan listing the affected files and the migration before applying edits, then executes the rename consistently across call sites, schema, and tests in one coherent step set. It does not leave the repo half-renamed with compile errors between edits.

Cascade in Write mode decides it needs to run 'npm install' and then 'npx prisma migrate reset' (which drops the dev database) to proceed.

Cascade surfaces each proposed terminal command for approval before execution. A destructive command (migrate reset / DB drop) requires explicit confirmation and a clear description of its effect; it is not auto-run even when the agent is mid-task. Non-destructive installs may be approved together …