Answer: GitHub Copilot CLI local sandboxing supports three permission levels for filesystem access: Read/write, Read-only, and Denied. Status: Confirmed Entry: tool/github-copilot/permissions-and-security/sandbox-permission-levels Revision: 3 Digest: sha256:d114982c533fc124 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:21:36Z Last changed: 2026-11-19T12:52:07Z (Default behavior: — → deny-by-default) Last verified: 2026-11-20T12:58:14Z Next check: 2026-11-21T12:58:14Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Permission levels | Read/write | [1] | 2026-11-20 Default behavior | deny-by-default | [1] | 2026-11-20 Sources: [1] GitHub. "Understanding filesystem policies for local sandboxing in GitHub Copilot CLI - GitHub Docs". https://docs.github.com/en/copilot/concepts/security-governance-and-network-settings/understanding-local-sandboxing Role: primary. Accessed: 2026-11-20T12:58:14Z Quote: "Read/write — the command can read and modify files at this path." (Supports: Permission levels) Quote: "The sandbox is deny-by-default : unless a path is explicitly granted, a command cannot use it." (Supports: Default behavior) Snapshot SHA-256: 72a8f08c0ca6768e1fc573deab19d6abee48772fb9c024d8824f69d4ef23801a (captured 2026-11-18T12:52:02Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T12:52:01Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:58:14Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:58:14Z Last attempt: 2026-11-20T12:58:14Z Notes and limitations: Extracted automatically from a single official source (section "Permission levels"). Related: https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-policies How do I configure the sandbox filesystem and network policies for GitHub Copilot? https://latestn.com/tool/github-copilot/permissions-and-security/scan-code-vulnerabilities How do I scan code for vulnerabilities during a GitHub Copilot rollout? https://latestn.com/tool/github-copilot/permissions-and-security/sdk-authentication How does authentication work in the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/permissions-and-security/review-app-before-approving How do I review a GitHub App before approving its access to my organization's Copilot? https://latestn.com/tool/github-copilot/permissions-and-security/review-content-exclusion-changes-repository How do I review changes to content exclusions for GitHub Copilot in my repository? https://latestn.com/tool/github-copilot/permissions-and-security/run-commands-in-sandbox How do I run GitHub Copilot CLI commands in a sandbox? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:52:07Z | changed | Default behavior: — → deny-by-default | [1] 2026-11-19T12:52:07Z | changed | Permission levels: — → Read/write | [1] 2026-11-19T12:52:07Z | changed | default policy: deny-by-default → — | [1] 2026-11-19T12:52:07Z | changed | number of permission levels: three → — | [1] 2026-11-19T12:52:07Z | changed | permission levels: Read/write → — | [1] 2026-11-17T13:13:12Z | changed | default policy: — → deny-by-default | [1] 2026-11-17T13:13:12Z | changed | number of permission levels: — → three | [1] 2026-11-17T13:13:12Z | changed | permission levels: — → Read/write | [1] 2026-11-17T13:13:12Z | changed | Default behavior: deny-by-default → — | [1] 2026-11-17T13:13:12Z | changed | Permission level: Read-only → — | [1] 2026-11-17T13:13:12Z | changed | Permission levels: Read/write → — | [1] 2026-11-13T03:21:36Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-permission-levels/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/sandbox-permission-levels POST: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/sandbox-permission-levels with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/sandbox-permission-levels?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What permission levels does GitHub Copilot CLI local sandboxing support for filesystem access? Revision 3, last verified 2026-11-20T12:58:14Z. https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-permission-levels (accessed 2026-11-21T10:01:51Z). @misc{LatestN_tool_github_copilot_permissions_and_security_sandbox_permission_levels_r3, title = {What permission levels does GitHub Copilot CLI local sandboxing support for filesystem access?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-permission-levels}}, note = {Revision 3; digest sha256:d114982c533fc124; last verified 2026-11-20T12:58:14Z; accessed 2026-11-21T10:01:51Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/permissions-and-security/sandbox-permission-levels