You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/first-second-parity-audit.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -206,7 +206,7 @@ Covered behavior:
206
206
-`Bash`/`PowerShell` foreground execution now distinguishes caller cancellation from timeout and ordinary nonzero exit in structured results: cancelled commands return `cancelled=true`, `timed_out=false`, `exit_code=-1`, and visible cancelled status text.
207
207
-`Bash` and Unix `PowerShell` process cancellation now sends SIGTERM to the managed process group first and uses a short `WaitDelay` SIGKILL fallback, allowing cooperative shell cleanup while still bounding ignored-signal commands.
208
208
-`BashOutput` now has the same 100k result budget surface as foreground `Bash`, so oversized background output is truncated in the visible tool result and persisted with `full_output_path` metadata.
209
-
-`Bash` and `PowerShell` background commands now emit tool progress events when the background task starts and finishes, carrying only task IDs, shell/status fields, exit/timed-out/cancelled state, duration, timestamps, and output byte counts without command text.
209
+
-`Bash` and `PowerShell` background commands now emit tool progress events when the background task starts and finishes, carrying only task IDs, shell/status fields, exit/timed-out/cancelled state, duration, timestamps, and output byte counts without command text; completed, timed-out, and cancelled finish paths are covered.
210
210
-`Bash`/`PowerShell` now accept the official `dangerouslyDisableSandbox` semantic boolean input and record it in structured results; full sandbox adapter and override execution semantics remain a separate incomplete parity area.
211
211
-`Bash`/`PowerShell` now surface `dangerouslyDisableSandbox` to the permission engine: normal/default/auto/plan/acceptEdits modes ask for confirmation, `dontAsk` denies it, and only available `bypassPermissions` mode allows it, preventing read-only classification or allow rules from silently approving sandbox override requests.
212
212
- Settings now propagate `sandbox.allowUnsandboxedCommands` into the permission context; when it is `false`, sandbox override requests are denied even in `bypassPermissions`, and settings validation flags non-boolean values for the known sandbox boolean fields.
0 commit comments