Source Intelligence

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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

SDK connections are told when model, mode, fast mode or effort changes

You'll notice
Useful3 Signal3
SDK

SDK clients are now re-told the model, mode, fast mode and effort whenever any of them change.

Feature flag
tengu_bridge_initialize_commands Not enough to say

Nothing 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.234: on

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

What

The bridge that carries a session to an SDK client now re-sends its init payload (model, permission mode, agents, skills, fast mode state and effort) whenever any of those change, not only at startup. Repeats are suppressed by a combined signature of the state, so an unchanged state does not announce again.

Details
  • Each announcement is recorded by bridge_sdk_state_announce telemetry, keyed by what triggered it.
  • The list of available commands is included only when tengu_bridge_initialize_commands is on; its fallback is off, so on this build the payload carries the rest of the state without commands.
Evidence

bridge_sdk_state_announce

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

See this entry in the whole of v2.1.234 →