Settings from your machine keep the environment's own files and report what was left out

What

When Claude Code sets up an environment using a pack of settings copied from your machine, it now behaves differently if that environment already has its own files:

• Unless the environment's files are being replaced, only your deny and ask permission rules (rules that block a tool or make Claude ask before using it) are applied. The environment's other settings are left in place. Before, the pack's settings were written whole.
• The notice now reads Settings from your machine were not applied instead of could not be applied.
• The notice now says when the environment keeps its own settings file, lists deny or ask rules left out because they were too long, too many or not plain, and lists files not written because the environment already has a file of the same name. Before, it only reported credential-related omissions and files not applied.
• The notice becomes a warning when any rules were left out (rulesLeftOut), and a new answersNotRestored condition replaces answersSettingsGone.
• The worker that applies the pack is now also admitted for runner children (runner_child) when sdkUrl is set and the engine admits them. Before, only managed cloud workers were admitted.

Why

Your safety rules from your machine still apply even when the environment already has its own configuration, and the notice now tells you why some of your rules or files did not carry over.