Skip to content

feat: minimal sandbox support in remote execution - #3520

Open
njskalski wants to merge 4 commits into
thought-machine:masterfrom
njskalski:remote-sandbox
Open

feat: minimal sandbox support in remote execution#3520
njskalski wants to merge 4 commits into
thought-machine:masterfrom
njskalski:remote-sandbox

Conversation

@njskalski

Copy link
Copy Markdown
Contributor

Hi,

I am using a custom sandbox and remote execution. This is a minimal patch that enables just that.

I believe most people have a separate profile for remote execution, where they can disable sandbox to keep the old semantics if desired.

Comment thread src/remote/action.go Outdated
Andrzej J Skalski added 2 commits May 12, 2026 17:17
Adds the missing section in config.html for the new Sandbox.Remote
field so that //docs/test:docs_test passes.
@njskalski

Copy link
Copy Markdown
Contributor Author

@sean- @toastwaffle Hi. I have addressed all comments you made. The feature is gated behind non-default setting. Can we merge it?

@peterebden peterebden left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty late on this one but it looks interesting...

I think the expectation here is that the remote worker will have the sandbox tool available? That is probably not unreasonable.

FWIW the approach we tool is that the remote workers always sandbox actions according to their own policies (and they know about the SANDBOX env var for some things), but that does require them to cooperate more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants