Permission rules in desk chats
Which permission rules a manager or general chat starts with, and when a changed rule applies.
01project permission rules#
A manager or general chat reads your user settings (--setting-sources user) and, on top of that, the permissions.allow, deny and ask rules from <chat dir>/.claude/settings.json, with settings.local.json in the same folder added after it. Nothing else from those files is carried: not hooks, env or plugins.
- The file read is
<chat dir>/.claude/settings.json, where the chat started. A parent folder's file is not read, and a latercddoes not change it. - A missing file carries nothing. A malformed one stops the chat from starting, with an error naming the file.
- The rules are written into a launch-generated
--settingsfile, which claude reads once at start. A rule you add mid-session applies after the chat's session restarts. - Delegated side chats are separate: they read the project settings through claude itself.