{"version":"2.1.295","anchor":"home-dir-now-optional-in-a-permissions-schema-remote-contro","canonical_anchor":"home-dir-now-optional-in-a-permissions-schema-remote-contro","heading":"Permission snapshot can leave out the home directory","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/home-dir-now-optional-in-a-permissions-schema-remote-contro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Permission snapshot can leave out the home directory\n\nhome_dir becomes optional in the permission snapshot and is omitted in one mode, and remote-control joins the reserved directory names\n\n**What**\n\nBefore deciding whether an action is allowed, Claude Code builds a snapshot of the facts the permission check needs, such as your home directory and the paths named in your rules. This release changes that snapshot.\n\n- `home_dir` is now optional in the snapshot's format. Before, it was required.\n\n- When a certain internal condition is true, the snapshot leaves out `home_dir` and skips rules that start with `~\/` (a shorthand for your home folder).\n\n- In that same case, each path is reported as just itself instead of being resolved through symlinks (shortcuts that point to another file or folder).\n\n- Separately, `remote-control` is added to a list of reserved directory names.\n\n**Why**\n\nThe finding describes these as small compatibility changes around remote control. In practice, in the affected mode, permission rules written with `~\/` are not resolved, and paths are checked as written rather than through the shortcuts they point to.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}