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.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Feedback and bug command availability checked in one place

Use it now
Useful2 Signal1
Slash Commands

The switches hiding /feedback and /bug now behave the same in menus and commands.

Feature flag
tengu_juniper_relay 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.251: on

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

DISABLE_FEEDBACK_COMMANDDISABLE_BUG_COMMANDCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC/feedback/bug
What

The rules that hide /feedback and /bug, namely DISABLE_FEEDBACK_COMMAND, DISABLE_BUG_COMMAND and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, now run through a single shared check that the feedback drafts entry in the settings menu also uses, so the menu and the commands can no longer disagree.

Details
  • The CLAUDE_CODE_SEND_FEEDBACK=true route additionally depends on a remote flag, tengu_juniper_relay, which falls back to off.
Evidence

DISABLE_FEEDBACK_COMMAND environment variable

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.251 →