Document VS Code sandbox errors in README troubleshooting - #73
Closed
MatanEden1 wants to merge 6 commits into
Closed
Document VS Code sandbox errors in README troubleshooting#73MatanEden1 wants to merge 6 commits into
MatanEden1 wants to merge 6 commits into
Conversation
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).
- 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.
Documents the MODULE_NOT_FOUND / EROFS / "no jf CLI server(s) found" failure when chat.agent.sandbox.enabled restricts the agent terminal to the workspace, and the sandboxBypass / setting-disable fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #74, which contains only the README change (this PR also carried the harness-vscode.md changes from the AX-1992-vscode-plugin-sandbox branch, which we're not shipping). |
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
1 participant
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
MODULE_NOT_FOUND,EROFS, and "no jf CLI server(s) found" when running MCP management under VS Code withchat.agent.sandbox.enabledon.harness-vscode.mdon this branch; this adds a matching entry to the README's Troubleshooting section so a human hitting the same errors finds the fix (sandboxBypass/ disabling the setting) without needing to ask support.Test plan