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.205 Home All releases ←olderv2.1.204 v2.1.206newer→
Claude Code v2.1.205

Fleet sidebar shows blocked-agent count

Feature flag
tengu_fleet_needs_input_nudge On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.205: on

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

When the tengu_fleet_needs_input_nudge feature flag is enabled, the fleet sidebar counter now:

  • Only activates when tengu_fleet_needs_input_nudge is enabled and the fleet sidebar is not already open; when the sidebar is open, the component renders a plain dim counter with no animation
  • Counts agents in a "blocked" tempo state that are not dismissed; the fleet state is polled every 10 seconds while at least one non-dismissed agent is present
  • Count display caps at "99+" for values above 99
  • When the needsInput count increases, the counter flashes warning color for 2,500 ms; simultaneously the fleet sidebar auto-focuses unless the user's current focus context is blurred
  • When the succeeded count increases (without a simultaneous new blocked agent), the counter flashes success color for 2,500 ms
  • Fires telemetry event tengu_fleet_nudge_state on every count change, reporting needs_input_count, done_count, succeeded_count, and an increased boolean
  • If the user opens the fleet sidebar within 2 minutes of a nudge firing, a success fleet_needs_input_nudge event is recorded; after 30 minutes without response, the nudge is logged as "ignored"
Evidence

Fleet nudge component (search for "tengu_fleet_needs_input_nudge") — H1e() at line ~792735; dNp store class at line ~792586; tengu_fleet_nudge_state telemetry at line ~792664

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