{"version":"2.1.296","anchor":"new-startup-check-for-own-user-settings-not-yet-served-serv","canonical_anchor":"new-startup-check-for-own-user-settings-not-yet-served-serv","heading":"Cloud sessions can wait on, and warn about, your own settings","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/new-startup-check-for-own-user-settings-not-yet-served-serv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Cloud sessions can wait on, and warn about, your own settings\n\nClaude Code now checks at startup whether your own settings differ from those cloud sessions use, and points to `claude apply-project-settings`\n\n**Unclear.** What decides whether this startup check runs at all was not identified.\n\n**What**\n\nBesides project hooks, Claude Code now also tells you about your own personal settings in cloud sessions. At startup it compares your user settings file with the settings it has been served for cloud sessions. If either cannot be read, or they differ, it reports that your settings are waiting to be applied.\n\nNew messages say:\n\n- Your own Claude Code settings are not used by cloud sessions, and your changes wait until you run `claude apply-project-settings`.\n\n- A note in the session warns that your allow rules, the rules that let actions run without asking, may not count.\n\n**Why**\n\nIf a cloud session seems to ignore your settings or allow rules, this tells you why and what command to run.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}