{"version":"2.1.299","anchor":"cronpermission-classifier-context-handles-missing-cwd","canonical_anchor":"cronpermission-classifier-context-handles-missing-cwd","heading":"Permission checks no longer send working-folder fields when the folder is unknown","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/cronpermission-classifier-context-handles-missing-cwd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Permission checks no longer send working-folder fields when the folder is unknown\n\n`live_cwd` and related folder fields are now left out of permission and classifier data when the current folder is unavailable\n\n**What**\n\nThe working folder (cwd) is the folder Claude Code is operating in. Some of the data Claude Code builds for permission decisions used to always include it, even when it was not known. Now these fields are only included when they have a value:\n\n- `live_cwd` and `trusted_directories.primary` in permission payloads, and `live_cwd` in a second payload that carries it.\n\n- `live_cwd`, `primary` and `rule_roots` in the context given to the permission classifier, the automatic checker that decides whether an action may go ahead (also used for scheduled cron tasks), when both the live and the original working folder are unavailable.\n\n**Why**\n\nIn practice, a session that has lost track of its working folder no longer sends empty or misleading folder values into permission checks. This affects what the auto-mode classifier sees after the folder is lost.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}