Skip to content

Document VS Code agent-sandbox filesystem restrictions - #70

Open
MatanEden1 wants to merge 5 commits into
mainfrom
AX-1992-vscode-plugin-sandbox
Open

Document VS Code agent-sandbox filesystem restrictions#70
MatanEden1 wants to merge 5 commits into
mainfrom
AX-1992-vscode-plugin-sandbox

Conversation

@MatanEden1

Copy link
Copy Markdown
Contributor

Summary

  • VS Code's agent-mode sandbox (chat.agent.sandbox.enabled) blocks filesystem access outside the workspace, which surfaces as Step 0 failures (MODULE_NOT_FOUND, unreadable ~/.jfrog/, EROFS on npm cache) that look like Agent Guard being disabled but aren't.
  • Adds a short ## VS Code's sandbox section to harness-vscode.md (mirrors the existing ## Codex's sandbox section) documenting the cause and the env-var credential workaround.

Test plan

  • Reviewer confirms the setting id and behavior described match current VS Code source/docs

The sandbox (chat.agent.sandbox.enabled) blocks read/write outside the
workspace, causing Step 0 to fail (MODULE_NOT_FOUND on the check script,
EROFS on npm cache, unreadable ~/.jfrog) in ways that look like Agent
Guard being disabled. Document the env-var credential workaround and
VS Code's sandbox-bypass confirmation as the fix.
Condense to the essential facts and workaround.
"Run once outside sandbox" is Copilot App's wording (a different
product), quoted in a still-open VS Code feature request (#333900)
asking VS Code to adopt it — not current VS Code UI text. VS Code
today shows only its generic tool-confirmation prompt. Verified
chat.agent.sandbox.enabled itself directly against VS Code source
(src/vs/platform/sandbox/common/settings.ts).
@MatanEden1
MatanEden1 requested a review from a team as a code owner September 3, 2026 06:43
- Env vars fix the ~/.jfrog/ credential path only; MODULE_NOT_FOUND
  (sandbox blocks reading the check script itself) needs the bypass/
  disable route instead. Split into two bullets.
- Name the actual confirmation mechanism (sandboxBypass: true / "Run
  in terminal outside the sandbox?"), verified against
  runInTerminalConfirmationTool.ts in microsoft/vscode.
- Note that MCP server env (${input:...}) is resolved by VS Code
  itself and unaffected by this sandbox.
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.

1 participant