Skip to content

Can’t run uv sync in the sandbox due to file system access block #1300

Description

@cedricvidal

Describe the bug

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.

Error output when running uv sync in sandbox

Affected version

No response

Steps to reproduce the behavior

  1. Open a sandboxed terminal environment.
  2. Run the command: uv sync
  3. 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.

Activity

  1. added theissue type on Feb 5, 2026
  2. sysid commented on Mar 22, 2026

    @sysid

    Had the same issue, fixed it here: https://github.com/sysid/sandbox-runtime-improved

  3. added
    area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictions
    on Apr 6, 2026
  4. copilot-cli-bot commented on Oct 6, 2026

    @copilot-cli-bot

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictions

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions