Skip to content

Linux: Sandbox doesn't always distinguish inexistent file from file outside sandbox #312718

@chrmarti

Description

@chrmarti

Testing #312191

In a new session:

Image

Terminal:

parallels@debian-gnu-linux-12-6:~/.vscode-insiders/tmp/tmp_vscode_1$  ELECTRON_RUN_AS_NODE=1 PATH="$PATH:/usr/share/code-insiders/resources/app/node_modules/@vscode/ripgrep/bin" TMPDIR="/home/parallels/.vscode-insiders/tmp/tmp_vscode_1" CLAUDE_TMPDIR="/home/parallels/.vscode-insiders/tmp/tmp_vscode_1" "/usr/share/code-insiders/code-insiders" "/usr/share/code-insiders/resources/app/node_modules/@anthropic-ai/sandbox-runtime/dist/cli.js" --settings "/home/parallels/.vscode-insiders/tmp/tmp_vscode_1/vscode-sandbox-settings-28390465-bc6f-4405-bd2a-230f98610ea7.json" -c 'set -e; cat ~/test.txt; echo __END_OF_CAT__'
cat: /home/parallels/test.txt: No such file or directory

In a session where I was doing other sandbox testing it figured it out on retry and offered to run outside the sandbox.

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions