Subagent report truncation accounting for a 'harness tail' section stays inert behind a flag.
New code paths, gated behind tengu_swift_whistle, control whether subagent SendMessage report truncation reserves extra budget for a harnessTail/inlineHandback section, and whether a telemetry counter fires when that path is taken. The logic is reachable from report formatting on agent completion and from mapToolResultToToolResultBlockParam for SendMessage, but the whole branch stays inert until the gate is enabled.
tengu_swift_whistle Not enough to sayNothing 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.261: 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.261. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Fixed SendMessage to an offline Remote Control session on another machine reading as delivered; the result now says delivery is queued until…
New in this build: tengu_swift_whistle