The switch controlling outcome codes in auto mode now runs through a wrapper with an empty branch.
An env-var branch for auto-mode outcome-code visibility looks stripped, leaving an empty conditional behind the setting.
tengu_auto_mode_config 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.221: 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.221. 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 four call sites that decide whether tool ids and outcome codes are rendered into the classifier transcript now go through a new accessor rather than reading the config directly.
- The wrapper contains an if statement with an empty body, so the env-var branch appears to have been stripped.
- It now unconditionally returns the same config value: CLAUDE_CODE_AUTO_MODE_OUTCOME_CODES if set, otherwise the
outcomeVisibilityfield of thetengu_auto_mode_configgate. - No behavioural difference found; noted only because it looks like a partially removed branch.
if (Ky.CLAUDE_CODE_AUTO_MODE_OUTCOME_CODES === void 0);
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Auto-mode setup confirmation is now a single keyboard form
Both mention auto mode
-
v2.1.229
Auto-mode setup wizard reduced to one screen
Both mention auto mode
-
v2.1.232
Auto-mode setup picks its own model and retries on a fallback
Both mention auto mode