{"version":"2.1.323","anchor":"await-claim-now-refused-with-blockfiletoolreadsoutsidework","canonical_anchor":"await-claim-now-refused-with-blockfiletoolreadsoutsidework","heading":"--await-claim no longer starts when file reads are limited to launch folders","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/await-claim-now-refused-with-blockfiletoolreadsoutsidework","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### --await-claim no longer starts when file reads are limited to launch folders\n\nStarting with --await-claim now fails if permissions.blockFileToolReadsOutsideWorkingDirectories is on\n\n**What**\n\nThe `--await-claim` flag, an option typed on the command line, starts a spare session that waits to be given a project. The `permissions.blockFileToolReadsOutsideWorkingDirectories` setting lets Claude read files only in the folders given at launch. A spare session is launched before its project is known, so the two do not fit together. Claude Code now stops with an error when both are used, and tells you to start the session in its project's folder instead.\n\n**Why**\n\nIf you combine these two options, startup now fails outright, so scripts or setups that use both need to change.\n\n- Area: Permissions\n- Names: `permissions.blockFileToolReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}