A gated fix can now remove stale leftover transcript entries when resuming a headless session
When resuming a print or headless (non-interactive) session, Claude Code now checks whether the message right after a resumed user message is itself followed only by system messages, using a new check. If so, that entry gets removed from the transcript, and the count of forwarded messages is adjusted to match.
This cleanup only happens when a setting called tengu_silly_waterfall is turned on for the account.
This is meant to prevent stale or orphaned transcript entries from lingering after a session resumes, keeping the conversation history clean.
tengu_silly_waterfall 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.271: 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.271. 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.
Nothing has been read yet about whether `tengu_silly_waterfall` is on for any account.
New in this build: tengu_silly_waterfall