{"version":"2.1.300","anchor":"cloud-settings-upload-status-levels-changed-missing-denyas","canonical_anchor":"cloud-settings-upload-status-levels-changed-missing-denyas","heading":"Fewer warnings when a cloud session reports on your uploaded settings","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cloud-settings-upload-status-levels-changed-missing-denyas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Fewer warnings when a cloud session reports on your uploaded settings\n\nThe cloud-settings notice now shows as a warning only when the check timed out or deny or ask rules are missing, and as a debug line otherwise\n\n**What**\n\nWhen a cloud session starts, Claude Code reports whether it applied your settings there. If the settings were not applied, that notice always used to be a warning.\n\nIts level now depends on what went wrong:\n\n- Info or warning when the check ran out of time.\n\n- Info or warning when your deny or ask rules are missing. These are permission rules that block a tool or make Claude ask you before using it.\n\n- Debug in every other case. Debug lines are kept for troubleshooting rather than shown as an alert.\n\nThe event that marks the cloud session as ready now also records whether deny or ask rules were missing.\n\n**Why**\n\nYou see fewer alarming notices. A warning still appears in the case that matters most, when the rules that keep tools in check did not make it into the cloud session.\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"}