{"version":"2.1.275","anchor":"sandbox-aware-write-permission-check-via-claude-code-sandbox","canonical_anchor":"sandbox-aware-write-permission-check-via-claude-code-sandbox","heading":"Sandbox-aware write-permission check via CLAUDE_CODE_SANDBOXED","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/sandbox-aware-write-permission-check-via-claude-code-sandbox","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Sandbox-aware write-permission check via CLAUDE_CODE_SANDBOXED\n\nWrite-permission checks now branch based on whether Claude Code is running sandboxed\n\n**What**\n\nClaude Code now uses a different check to decide whether a file can be written to depending on whether the `CLAUDE_CODE_SANDBOXED` environment variable is set. Inside a sandbox, one internal check is used; outside of it, a different one applies. A related addition drains any pending write queues before this decision is finalized.\n\n**Why**\n\nThis lets Claude Code apply the correct write-permission logic depending on whether it's running inside a sandbox (a restricted environment that limits what a process can access), rather than using one check for both situations.\n\n- Area: Sandbox\n- Names: `CLAUDE_CODE_SANDBOXED`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}