Skip to content

Disable signal-triggered Inspector in sandbox runners - #31

Merged
jacobprall merged 1 commit into
mainfrom
codex/issue-21-disable-runner-inspector
Oct 28, 2026
Merged

jacobprall merged 1 commit into
mainfrom
codex/issue-21-disable-runner-inspector

Conversation

@starmorph

Copy link
Copy Markdown
Contributor

Same-user tool processes can signal the credential-holding Node runner to activate Inspector, bypassing the protection provided by its execute-only binary. Launch the runner with --disable-sigusr1 through a shared as-runner.sh --node path used by investigations and verification probes.

The installer requires Node >=22.19 with actual flag support. Runtime verification sends a same-user signal and checks that Inspector remains inactive, alongside the existing /proc isolation check. Unsupported runtimes and launches that strip the flag fail verification.

Validation:

  • The runtime-script regression reproduced inspectorActive: true before the fix and returns false afterward.
  • Focused sandbox tests: 25 passed. Shell syntax checks passed.
  • Independently reran typecheck and the full suite: 82 passed, 1 live-model test skipped. git diff --check passed.

Rollout requires a successful snapshot refresh; deploying services alone does not update scripts already captured in snapshots. Live Render identity and loopback behavior were not exercised locally.

Fixes #21.

@jacobprall
jacobprall merged commit 0bf9fad into main Oct 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

[P1] Disable signal-triggered Inspector on the credential-holding runner

2 participants