Chrome auto-mode safety floor is decided differently in remote sessions
For the Chrome auto-mode classifier floor, remote sessions now read the server setting a different way, while CLAUDE_CHROME_CLASSIFIER_FLOOR still overrides it
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release
Unclear What the different way of reading the setting changes for remote sessions is not stated.
What
When Claude controls Chrome in auto mode, a classifier floor setting applies. A classifier is a background check that judges actions. How Claude Code decides whether this floor is on has changed:
In remote sessions, where CLAUDE_CODE_REMOTE is set, the server setting is now read in a different, safer way.
In local sessions it is read as before, falling back to off when the server sends nothing.
The server setting has read on for this site's account and for an anonymous check.
Why
This changes how the Chrome auto-mode floor is settled in cloud sessions.
Read from
Feature flag
tengu_cowork_chrome_automode_defaultOff by default, switched on for this account
The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.296: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
