{"version":"2.1.299","anchor":"chrome-floor-block-now-asks-the-user-in-auto-mode","canonical_anchor":"chrome-floor-block-now-asks-the-user-in-auto-mode","heading":"Some actions blocked by auto mode now ask you instead","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/chrome-floor-block-now-asks-the-user-in-auto-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Some actions blocked by auto mode now ask you instead\n\nSome actions blocked by the permission checker now ask you first, defaulting to No; the `chromeFloorBlockPrompts` setting can turn this off\n\n**What**\n\nClaude Code uses an automatic checker (the classifier) to judge whether an action is safe. For one kind of block, which Claude Code calls a Chrome-floor block, it can now ask you instead of simply refusing. The question:\n\n- must be answered by a person, not by automation\n\n- defaults to No\n\n- does not offer an always-allow option\n\nThis happens only when all of these hold:\n\n- you are present to answer\n\n- the permission mode is default or acceptEdits\n\n- Claude Code is talking over standard input and output\n\n- the session can show prompts\n\n- the `chromeFloorBlockPrompts` setting is not set to false\n\n**Why**\n\nYou can now decide on some actions that would otherwise just be blocked, and you can set `chromeFloorBlockPrompts` to false to keep them blocked.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}