{"version":"2.1.242","anchor":"cloud-sessions-report-which-host-settings-they-ignored","canonical_anchor":"cloud-sessions-report-which-host-settings-they-ignored","heading":"Cloud sessions report which host settings they ignored","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/cloud-sessions-report-which-host-settings-they-ignored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Cloud sessions report which host settings they ignored\n\nA cloud session now reports which of your flags and settings keys it ignored.\n\n**What**\n\nThe startup message a cloud-hosted session sends back now includes a `not_applied` list, so a tool driving Claude Code can show you once that a command-line flag, a settings key or a startup field was ignored.\n\n**Details**\n\n- Each entry has a `name` of the form `--flag`, `settings.<key>`, `managed-settings.<key>` or `initialize.<field>`, plus a `kind` of `lost`, `kept` or `preference`. `kept` means attaching to an existing session kept that session's configuration instead.\n- Capped at 40 entries, with `lost` ones listed first.\n- Present only on startup messages from the headless stream-json client of a cloud-hosted session, and absent in every other mode.\n\n**Evidence**\n\n`` `not_applied`, when present, lists what the host passed that this session does not apply ``\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}