{"version":"2.1.307","anchor":"await-claim-error-now-names-subprocess-sandbox-conflict-u","canonical_anchor":"await-claim-error-now-names-subprocess-sandbox-conflict-u","heading":"--await-claim still refuses to run with CLAUDE_CODE_SUBPROCESS_ENV_SCRUB","tier":"internal","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/await-claim-error-now-names-subprocess-sandbox-conflict-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### `--await-claim` still refuses to run with `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB`\n\nThe refusal of `--await-claim` alongside `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB` is unchanged, with the same error text as before\n\n**What**\n\nClaude Code still stops at startup when the `--await-claim` flag is used with the `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB` environment variable set. The error message is the same as before: \"--await-claim cannot be used with CLAUDE_CODE_SUBPROCESS_ENV_SCRUB: the subprocess sandbox pins its protected paths to the launch directory at start-up.\"\n\n**Why**\n\nThe code behind this check was reorganised but the behaviour did not change, so any script that already avoids this combination needs no update.\n\n- Area: Agents\n- Names: `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}