Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.233entry #3

Claude Code v2.1.233 ·

Plugin eval tells the model the env var that turns it on

Setting CLAUDE_CODE_WALNUT_SPIRE=1 turns on the early-access plugin eval command.

Use it now Notable In Development
JSON All of v2.1.233
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Plugin EvalArea: what it touches
In DevelopmentKind: in v2.1.233,
What probably matters to youSection of the release
What

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.

Details
  • The gate itself is unchanged: the remote flag tengu_walnut_spire, which defaults to off, or the environment variable.
Evidence

CLAUDE_CODE_WALNUT_SPIRE=1

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_WALNUT_SPIREclaude plugin eval
Feature flag
tengu_walnut_spire Off in both readings

The 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: 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.233. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Create and distribute a plugin marketplace touched a line naming claude plugin eval after this was published. Test your marketplace before sharing. Validation checks file structure; to test whether a plugin changes what Claude does on realistic prompts, run its eval suite with [`claude plugin eval`](/docs/en/plugin-evals) before you publish a new … plugin-marketplaces see the edit
Confirmed since Anthropic's documentation has since written up claude plugin eval, on Claude Code changelog. * Added `claude plugin eval`: run a plugin's eval suite against Claude Code and get scored, reproducible results (JSON + HTML report); see `claude plugin eval --help` changelog see the edit
What has happened since
Flag reading moved The flag server now returns off for tengu_walnut_spire, read as this account. 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.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_walnut_spire, read as this account. 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.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude plugin eval, on Claude Code changelog.

See this entry in the whole of v2.1.233 →

Feedback