Enable edit and bash tools by default when sandbox is enabled #9065
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 sandbox is enabled (either explicitly via
sandbox.agentor auto-enabled via network restrictions), agents now automatically receive file editing and bash command capabilities without explicit tool configuration.Changes
Modified
applyDefaultTools()signatureSandboxConfigandNetworkPermissionsparameters to detect when sandbox is activeisSandboxEnabled()helper to check sandbox state (explicit config or auto-enablement)Default tool injection
When the sandbox is enabled:
tools.edit: true- enables file editingtools.bash: ["*"]- enables all bash commandsThe sandbox is considered enabled when:
sandbox.agentis explicitly set (awf/srt)sandbox.type: srtis configuredExplicit tool configuration overrides these defaults.
Example
Before:
After:
Or with explicit sandbox:
Behavior Matrix
sandbox.agent: awfsandbox.agent: srtsandbox.agent: falsetools:Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.