The rule stopping Claude publishing artifacts you didn't ask for can now be removed remotely.
tengu_umber_sluice Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.247: on
Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The permissions text used by auto mode now ships as an embedded file, and a new switch decides whether the rule telling Claude not to publish artifacts you did not ask for stays in that text. The environment variable CLAUDE_CODE_AUTO_MODE_ARTIFACT_CONSENT_RULE wins if set; otherwise a remote feature flag named tengu_umber_sluice decides, with a compiled-in fallback of off. The mapping is inverted, so off keeps the rule in the prompt and only a server value of on removes it, meaning the rule is on by default and the flag exists solely to turn it off remotely.
- The variant is chosen once when the session enrolls in auto mode and threaded through later calls, so a session does not switch behaviour mid-flight.
- The chosen variant is recorded and re-announced to listeners if it does change during a session.
- Every auto-mode classification result, including fallback and retry paths, reports which variant it ran under; with the flag off the recorded value is that the rule is applied.
- The code that strips the rule refuses to act if the matched line is shorter than a reflow floor, or if a mention of the rule survives the removal; in either case it logs the refusal and serves the text with the rule still present.
Unrequested Artifact Publish, artifactConsentRuleArm
Strings lifted out of the shipped bundle, so the claim above can be checked against them.