Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.235 Home All releases ←olderv2.1.234 v2.1.236newer→
Claude Code v2.1.235

plugin eval can be pointed at a different case directory

Use it now
Useful3 Signal4
Plugins Notable not in their notes

Point plugin eval at any case directory with --eval-dir, still behind an early-access gate or env var.

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.235: on

Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you

--eval-dirCLAUDE_CODE_WALNUT_SPIREplugin evalplugin eval init
What

The plugin evaluation harness no longer hard-codes evals/. A new --eval-dir <dir> flag, or an experimental.evals key in plugin.json, chooses the case directory, and results land in <plugin>/<dir>/results/. A list is accepted and its first entry wins. Both plugin eval and plugin eval init stay behind early access: the gate tengu_walnut_spire (fallback false) or the env var CLAUDE_CODE_WALNUT_SPIRE. Without it the commands are filtered from the command list and report "currently in early access".

Details
  • Manifest values are validated hard: relative only, no .., at most 200 characters and 8 path segments, plain segment names, not a bare filename, no reserved Windows device names, trailing dot or space, or :.
  • The path may not sit inside a loaded component directory or route through node_modules, .claude or results.
  • A top-level "evals" key is detected and reported as misplaced rather than used.
Evidence

must stay inside the plugin root (no ..), Directory of eval cases for the plugin evaluation harness, relative to the plugin root (default: evals/). A list is accepted; its first entry is the case directory.

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.

See this entry in the whole of v2.1.235 →