A new remote flag, on by default, reassembles split message-tool inputs when they are read back.
tengu_deep_feather 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.236: off
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
tengu_deep_feather is new and its fallback is true, so absent a server value it is on for everyone. It governs whether split message-tool inputs are reassembled, both when the tool reads its own input and when a prior tool call is re-read to recover its original message and idle-subscription values.
- Effectively a kill switch: if remote config turns it off, previously split inputs stop being reassembled on the round trip.
- Notable as the only new flag here that defaults on rather than off.
tengu_deep_feather
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Wake routing and cross-session notices rewritten off UI effects
Both mention multi
-
v2.1.246
Multi-agent reply pairing now rejects and counts suspicious matches
Both mention multi
-
v2.1.239
Worker agents told to review, test, commit and report a PR link
Both mention multi