Repository navigation
Clarify shell sandbox unavailability and recovery - #257
Merged
Merged
Conversation
qduc
force-pushed
the
codex/sandbox-availability-guidance
branch
from
November 12, 2026 01:05
ecc0cea to
b0c48ee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the shell sandbox cannot start because a dependency or initialization is unavailable, Term2 currently says the sandbox blocked the command. That suggests a policy denial even though the command never ran, and encourages retries that cannot fix the runtime.
Report that the command was not run and that the sandbox issue needs to be resolved before a sandboxed retry. Keep the optional one-shot unsandboxed request explicitly conditional on policy and interactive user approval. Actual command-denial guidance and all approval and execution checks remain unchanged.
Validation: focused run_code shell integration (15 passed), typecheck, lint (40 existing warnings), provider black-box suite (270 passed, 5 skipped), and independent verification of unavailable-dependency, unsupported-platform and initialization-failure refusal/recovery, approved and denied escape, and actual-denial guidance. The independent failure and recovery probes inject sandbox conditions rather than reproducing an OS outage. This is a task-independent diagnostic fix; no end-to-end token or cost improvement is claimed.