Setting CLAUDE_CODE_WALNUT_SPIRE=1 turns on the early-access plugin eval command.
tengu_walnut_spire 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.233: on
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.233. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When the early-access claude plugin eval command is enabled, Claude is now told the enabling variable is CLAUDE_CODE_WALNUT_SPIRE=1, settable in your shell or in the env block of user or managed settings, for machines outside the per-organization rollout. When it is not enabled, Claude is told to call it early access and never guess a variable name.
- The gate itself is unchanged: the remote flag
tengu_walnut_spire, which defaults to off, or the environment variable.
CLAUDE_CODE_WALNUT_SPIRE=1
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.235
plugin evalcan be pointed at a different case directoryBoth mention walnut spire eval