The check for a speculative permission classifier on remote tools (tools run on another machine) is now connected to the code that would use it. It reads a new environment variable, a setting you put in your shell, CLAUDE_CODE_REMOTE_TOOLS_SPECULATIVE_CLASSIFIER, along with a remote switch. Whatever either of them says, the check still always answers no, so setting the variable has no effect in this build.
The remote switch has answered on for this site's own account in earlier readings. That makes no difference here, because the check ignores it.
The name suggests a planned classifier that would judge permission for remote tool use ahead of time. It is wired in but disabled in the code itself.
tengu_violin_speculative_classifier Off by default, switched on for this accountThe 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.282: 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.
Read once, for one account on one subscription tier, against v2.1.282. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
What the classifier path would do once enabled is not shown.
New in this build: tengu_violin_speculative_classifier