You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Can’t run uv sync in the sandbox due to file system access block #1300
When I try to run uv sync in a sandboxed environment, the command fails due to blocked file system access. The sandbox prevents the command from accessing the required cache directory, resulting in an error. See the attached screenshot for details.
Affected version
No response
Steps to reproduce the behavior
Open a sandboxed terminal environment.
Run the command: uv sync
Observe the error indicating failure to access the required cache directory.
Expected behavior
uv sync should be able to run successfully in the sandbox, or provide a clear message if file system access is not permitted.
Additional context
Terminal output indicates: "failed to open file... os error 1".
System: macOS using a sandboxed environment.
Issue presented in project: github/copilot-cli.
This appears to be resolved as of GitHub Copilot CLI v1.0.92. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.
Activity
sysid commentedon Mar 22, 2026
Had the same issue, fixed it here: https://github.com/sysid/sandbox-runtime-improved
copilot-cli-bot commentedon Oct 6, 2026
This appears to be resolved as of GitHub Copilot CLI v1.0.92. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.