Repository navigation
Route sandbox commands by tool profile - #228
Merged
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
Adds automatic sandbox profile routing so command-capable tools choose the right Podman container from tool intent instead of requiring users to switch sandbox profiles manually.
run_bashuses the default sandbox profile from[sandbox].image[sandbox].documents_imageRelated issue
None.
How was this tested?
go test ./internal/agent ./internal/agentruntime ./internal/config— passesgo test ./...— passesgo vet ./...— passesgovulncheck ./...— no reachable vulnerabilitieslsp_changed_files_diagnostics— no compile diagnostics; one non-blocking stale style hint remained after applying the suggestederrors.AsTypeshapeChecklist
go test ./...passesgo vet ./...is cleangovulncheck ./...reports no reachable vulnerabilitiesdocs/guide)