Bug/Feat: Sandbox config to selectively enable tools
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the feature or problem you'd like to solve
Feature Request: Sandbox config in settings.json to selectively enable tools, and/or whitelist bundled copilot package tools
Proposed solution
potentially have some tools { ... } within sandbox section in settings.json to enable allowed tools/apps/executables
(or provide documentation on how best to accomplish this if fits somehow in current schema)
more specifically, encountered this around copilot bundled rg ripgrep, while in sandbox enabled:
Search "xunit\.V3" (sandboxed) sh: 1:~/.copilot/pkg/linux-x64/1.0.75/ripgrep/bin/linux-x64/rg: not found
Search is blocked because the bundled rg executable is unavailable under the current sandbox policy.
Please review /sandbox and retry.
ideally specifically around this, executable packages that are bundled within distributed copilot are just marked "safe" by default and end user does not need to do anything additional to whitelist to allow these in sandbox mode
Example prompts or workflows
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the settings.json configuration and the /sandbox policy behavior, then trace how the bundled executable at ~/.copilot/pkg/linux-x64/1.0.75/ripgrep/bin/linux-x64/rg is checked. Determine whether the existing schema can express allowed tools or whether bundled tools need a safe default; done means the intended configuration or documentation is defined and sandboxed Search can use rg.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, shell
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100