Skip to content

Document VS Code sandbox errors in README troubleshooting #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MatanEden1 wants to merge 6 commits into from
Closed

Document VS Code sandbox errors in README troubleshooting #73

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
d290434
Document VS Code agent-sandbox filesystem restrictions
MatanEden1 Sep 3, 2026
1e8bc21
Trim VS Code sandbox note
MatanEden1 Sep 3, 2026
98be2f4
Fix inaccurate sandbox-bypass prompt wording
MatanEden1 Sep 3, 2026
e53afec
Address PR review: split MODULE_NOT_FOUND from credential fix
MatanEden1 Sep 3, 2026
74671b0
Trim VS Code sandbox note wording
MatanEden1 Sep 3, 2026
3df417c
Add README troubleshooting entry for VS Code sandbox errors
MatanEden1 Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,6 +236,10 @@ The JFrog MCP is a remote HTTP server the plugin attaches at `https://${env:JFRO

If the agent keeps falling back to the `jf` CLI even though the JFrog tools are present, it usually means the tools aren't selected in the picker — enable them and start a new chat. Make sure `JFROG_PLATFORM_URL` is set in the IDE launch environment so `https://${env:JFROG_PLATFORM_URL}/mcp` resolves correctly.

### MCP management fails with `MODULE_NOT_FOUND`, `EROFS`, or "no jf CLI server(s) found"

This happens when VS Code's `chat.agent.sandbox.enabled` setting is on: it restricts the agent's terminal commands to the workspace folder, and the skill's helper script and your `jf` config live outside it. Fix: when prompted, choose **"Run in terminal outside the sandbox?"**, or disable `chat.agent.sandbox.enabled` in VS Code settings.

---

## Support
Expand Down
14 changes: 14 additions & 0 deletions plugin/skills/jfrog-mcp-management/references/harness-vscode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,20 @@ Rules for the `inputs` block:
- `description`: use the catalog `description`; if empty, construct a brief one.
- `Bearer` headers: use `"Bearer ${input:<id>}"` and ask only for the token.

## VS Code's sandbox

`chat.agent.sandbox.enabled` blocks filesystem access outside the workspace
for the agent's terminal commands only — MCP server `${input:...}` values are
resolved by VS Code itself and unaffected.

- `MODULE_NOT_FOUND` on Step 0's script: the script itself is unreadable, env
vars won't help. Re-run with `sandboxBypass: true` ("Run in terminal
outside the sandbox?") or disable `chat.agent.sandbox.enabled`.
- Unreadable `~/.jfrog/` (Unknown) or `EROFS` on the npm cache: unlike Codex,
env vars pass through the sandbox — prefer `JFROG_URL` +
`JFROG_ACCESS_TOKEN` ([agent-guard-common.md](agent-guard-common.md)) over
`--server`; same bypass fallback otherwise.

## Enable

Writing the entry is not enough — the server must be started via the UI. If it
Expand Down
Loading