Repository navigation
Run OpenWorker inside an OpenShell sandbox - #723
Merged
Merged
Conversation
…t the proxy look names up With OPENSHELL_SANDBOX=1 the agent is pointed at OpenShell's policy skill when it exists, and at the openshell command when it does not. web_fetch hands a name to OpenShell's proxy; a literal internal address is still refused.
…between retries A failed model call prints what was underneath it, such as a proxy's 403. SIGTERM during the wait before a retry now stops the run and leaves its record (exit 130).
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
1 participant
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 OpenWorker runs inside an OpenShell sandbox, the agent is told what a blocked request means and web fetches go through the sandbox's proxy;
openworker runalso shows why a model call failed and stops cleanly on a stop signal.