{"version":"2.1.236","anchor":"a-new-remote-flag-on-by-default-controls-message-input-split","canonical_anchor":"a-new-remote-flag-on-by-default-controls-message-input-split","heading":"A new remote flag, on by default, controls message-input split repair","tier":"internal","area":"Multi-Session","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/a-new-remote-flag-on-by-default-controls-message-input-split","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### A new remote flag, on by default, controls message-input split repair\n\nA new remote flag, on by default, reassembles split message-tool inputs when they are read back.\n\n**What**\n\n`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.\n\n**Details**\n\n- Effectively a kill switch: if remote config turns it off, previously split inputs stop being reassembled on the round trip.\n- Notable as the only new flag here that defaults on rather than off.\n\n**Evidence**\n\n`tengu_deep_feather`\n\n- Flag `tengu_deep_feather`: Not enough to say (read for one account on one subscription tier against v2.1.236; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Multi-Session\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}