{"version":"2.1.283","anchor":"new-permission-denial-reason-no-working-directory","canonical_anchor":"new-permission-denial-reason-no-working-directory","heading":"Permission checks can now fail because a session has no working directory","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-permission-denial-reason-no-working-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Permission checks can now fail because a session has no working directory\n\nA permission check can now be refused with a message saying it needs a working directory and the session has none\n\n**Unclear.** Which sessions have no working directory is not known.\n\n**What**\n\nClaude Code can now refuse a permission check with the message \"permission check needs a working directory; the session has none\". The working directory is the folder a session runs in.\n\n**Why**\n\nA session without a project folder gets a clear refusal instead of an unexplained one.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}