{"version":"2.1.283","anchor":"permission-check-with-no-working-directory-now-denies-instea","canonical_anchor":"permission-check-with-no-working-directory-now-denies-instea","heading":"Tool calls are denied clearly when a session has no working folder","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/permission-check-with-no-working-directory-now-denies-instea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Tool calls are denied clearly when a session has no working folder\n\nIf a permission check needs a working folder and the session has none, the tool call is now denied with an explicit message, and retries are too\n\n**What**\n\nBefore Claude runs a tool (an action such as editing a file or running a command), Claude Code checks whether it is allowed. Some of those checks need a working folder. If the session has none, the call is now denied with a message saying the check needs a working folder and this session has none, and that a retry will be denied the same way. Before, the error was logged and a fallback handler took over.\n\n**Why**\n\nSessions without a working folder, such as some SDK or remote setups, now get a clear and predictable denial instead of an unclear fallback.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}