{"version":"2.1.280","anchor":"hardcoded-long-turn-nudge-default-preset-removed","canonical_anchor":"hardcoded-long-turn-nudge-default-preset-removed","heading":"Hardcoded 'long turn nudge' default preset removed","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/hardcoded-long-turn-nudge-default-preset-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Hardcoded 'long turn nudge' default preset removed\n\nThe long-turn nudge feature no longer accepts a simple on\/off setting; it now requires a full config object\n\n**What**\n\nThe \"long turn nudge\" feature, controlled by the remote gate `tengu_rc_long_turn_nudge`, previously allowed that gate to just be set to `true`, which mapped to a hardcoded default configuration (a 90-second threshold, probability 1, a maximum of 3 impressions, and a 7am-9pm active window). That shorthand has been removed; only an explicit configuration object now takes effect.\n\n**Why**\n\nThis removes the implicit default behind a bare `true` value, meaning the nudge now requires explicit configuration to behave as before rather than falling back to hardcoded defaults.\n\n- Flag `tengu_rc_long_turn_nudge`: Not enough to say (read for one account on one subscription tier against v2.1.280; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}