{"version":"2.1.280","anchor":"tengu-kairos-ready-nudge-no-longer-treats-bare-true-as-ful","canonical_anchor":"tengu-kairos-ready-nudge-no-longer-treats-bare-true-as-ful","heading":"tengu_kairos_ready_nudge no longer treats bare true as full-probability enable","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tengu-kairos-ready-nudge-no-longer-treats-bare-true-as-ful","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### tengu_kairos_ready_nudge no longer treats bare `true` as full-probability enable\n\nThe kairos ready nudge config no longer treats a bare `true` value as an automatic full-probability enable\n\n**What**\n\nThe remote-configuration gate controlling the 'kairos ready' nudge used to have a shortcut: if the config value was simply `true`, it was treated as `{probability: 1, maxImpressions: 5, impressionKey: \"\"}`. That shortcut has been removed. Now a bare `true` value falls through to the normal object-shape validation, which likely results in the config being treated as invalid (returning null) instead.\n\n**Why**\n\nThis removes a special case that let a simple boolean stand in for a full configuration object, meaning the nudge's settings now need to be specified in their proper object form to take effect.\n\n- Flag `tengu_kairos_ready_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"}