{"version":"2.1.295","anchor":"cloud-settings-seed-reports-unreadable-settings-files-and-gi","canonical_anchor":"cloud-settings-seed-reports-unreadable-settings-files-and-gi","heading":"Cloud sessions now name the settings file that could not be read","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-settings-seed-reports-unreadable-settings-files-and-gi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Cloud sessions now name the settings file that could not be read\n\nWhen settings do not reach a cloud session, Claude Code now names the broken settings file and tells you to fix it and reopen\n\n**What**\n\nWhen you start a cloud session (Claude Code running on a remote machine instead of yours), Claude Code copies some of your settings across and tells you what it did not send.\n\nThat notice is now more specific:\n\n- If a settings file could not be read, the notice names that file and says to fix it, then reopen this cloud session or start a new one. Before, it only mentioned \"your settings file, which failed validation\".\n\n- For allow rules that were kept, the warning now says that \"a hook, a plugin or a rule that was not sent may guard\" the action.\n\n**Why**\n\nYou can see exactly which file kept your settings from reaching the cloud, and what to do about it, instead of guessing.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}