Harden approval-gated code execution and recovery - #132
Merged
Conversation
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.
Summary
Why
The existing feature is an approval-gated bounded Python runner, not yet a repository coding agent. The audit found several reliability boundaries that needed to be closed before expanding it:
Implementation notes
process_capability_unavailable; filesystem/network code remains within the existing bounded worker.Validation
backendandtestsFollow-up boundary
This PR deliberately does not claim full coding-agent parity. The remaining transactional run engine and workspace-agent work is sequenced with release gates in
docs/CODING_AGENT_HARDENING_ROADMAP.mdso future passes remain finite and auditable.