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.222 Home All releases olderv2.1.221 v2.1.223newer

Byte watchdog covers first-party, gateway and Bedrock streams

Use it now
Useful4 Signal0
Streaming Notable not in their notes

Stalled streams are now detected across direct, gateway and Bedrock connections, and you can force it with an env var.

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

CLAUDE_ENABLE_BYTE_WATCHDOGCLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK
What

The rule for wrapping a text/event-stream body in the stall watchdog was widened from a single caller-supplied boolean to name the providers explicitly.

Details
  • Now instruments firstParty, gateway and anthropicAws responses.
  • Gated on tengu_stream_watchdog_default_on, which falls back to true when the flag is unavailable.
  • CLAUDE_ENABLE_BYTE_WATCHDOG overrides the decision, and CLAUDE_ENABLE_BYTE_WATCHDOG_BEDROCK covers Bedrock specifically.
Evidence

tengu_stream_watchdog_default_on

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