What
Auto mode lets Claude act without asking each time, using a classifier, a model that judges each action. Computer use means Claude controlling a desktop by clicking and typing. New code, controlled by server-side switches, prepares closer review of these actions and of browser actions.
- Allow rules: when the check is on, a computer-use action that changes something (not an observe or access action, and not a served call) is no longer approved straight away by an allow rule for the whole tool, and the shortcut that skips further checks is suppressed. The action goes on through the rest of the permission checks.
- Classifier routing: computer-use calls can be kept out of the "would be allowed in acceptEdits" and "safe allowlist" shortcuts so the classifier judges them. The skip for calls that come from a plugin no longer applies to certain tool names.
- The check is on when
tengu_quirky_shoreis "on" (fallback "off") or thecomputerUseCheckskey is true in thetengu_drifting_reefsettings object. - Action summaries: the Chrome
computerandform_inputtools,browser_batchitems and computer-use tools can gain anaction_summaryfield asking Claude for a few words on what each action does, for example "Sets the delivery date to 29 September". The field asks for the effect only, with no reasons and no passwords or other secrets. - For Chrome this is switched on by
chromeAgentNoteintengu_auto_mode_configor thebrowserSummarykey oftengu_drifting_reef. For computer use, bycomputerUseAgentNoteor thecomputerUseSummarykey. - The classifier's records gain fields for these computer-use and summary details.
Nothing has been read about tengu_quirky_shore or tengu_drifting_reef for this release, and no reading of tengu_auto_mode_config has been taken under it.
Why
When switched on, clicks and typing in auto mode would be checked even if you allow-listed the whole computer-use tool, and short summaries would give a readable line for each browser or desktop action. Until the switches are on, behaviour may not change.
tengu_quirky_shore Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.284: not a boolean we can read
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.
tengu_drifting_reef Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.284: not a boolean we can read
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.
Read once, for one account on one subscription tier, against v2.1.284. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear what reviews these actions once they go past the allow rule, whether an automatic classifier or a prompt to you.
New in this build: tengu_drifting_reef