diff --git a/plugin/skills/jfrog-mcp-management/references/harness-vscode.md b/plugin/skills/jfrog-mcp-management/references/harness-vscode.md
index 2c0b61f..8374dfe 100644
--- a/plugin/skills/jfrog-mcp-management/references/harness-vscode.md
+++ b/plugin/skills/jfrog-mcp-management/references/harness-vscode.md
@@ -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