{"version":"2.1.288","anchor":"tengu-gleaming-rivest-check-replaced-by-a-helper","canonical_anchor":"tengu-gleaming-rivest-check-replaced-by-a-helper","heading":"SDK prompt-suggestions opt-in now goes through a shared check","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/tengu-gleaming-rivest-check-replaced-by-a-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### SDK prompt-suggestions opt-in now goes through a shared check\n\nWhen a program restarts a session through the SDK, the check deciding whether to turn on prompt suggestions now runs through a shared helper\n\n**Unclear.** It is not known whether the helper still reads the same remote setting or what it falls back to.\n\n**What**\n\nWhen a program using the SDK (a toolkit for building on top of Claude Code) asks a session to re-initialize and requests prompt suggestions, the decision about whether to honour that request no longer reads the remote setting directly at that point. It now goes through a shared helper function.\n\n**Why**\n\nThe behaviour may be unchanged, but what decides whether suggestions get turned on may now come from a different place.\n\n- Flag `tengu_gleaming_rivest`: Not enough to say (read for one account on one subscription tier against v2.1.288; 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: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}