{"version":"2.1.274","anchor":"new-gate-tengu-tidy-fern-controls-an-alternate-user-message","canonical_anchor":"new-gate-tengu-tidy-fern-controls-an-alternate-user-message","heading":"New gate tengu_tidy_fern controls an alternate user-message construction path","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-gate-tengu-tidy-fern-controls-an-alternate-user-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New gate tengu_tidy_fern controls an alternate user-message construction path\n\nNew gate tengu_tidy_fern can add an extra value into how user messages are built\n\n**Unclear.** Nothing has been read about the tengu_tidy_fern gate, and what the extra computed value actually does isn't stated.\n\n**What**\n\nA new internal flag, `tengu_tidy_fern`, controls whether an extra value is computed and passed along when Claude Code builds a user message for tool use. Previously this value was always left empty; now, when the flag is on, it is computed via a new function and included instead.\n\n**Why**\n\nThe finding doesn't say what this extra value is used for, so it's unclear what practical difference this makes for a user.\n\n- Flag `tengu_tidy_fern`: Not enough to say (read for one account on one subscription tier against v2.1.274; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Elsewhere\n- Names: `tengu_tidy_fern`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}