{"version":"2.1.318","anchor":"gates-tengu-curried-trinket-added-to-gate-lists","canonical_anchor":"gates-tengu-curried-trinket-added-to-gate-lists","heading":"An unexplained experiment and beta entry are wired up","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/gates-tengu-curried-trinket-added-to-gate-lists","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### An unexplained experiment and beta entry are wired up\n\nClaude Code now checks a remote experiment setting and can send one more beta feature request, but what either one does is not known\n\n**Unclear.** What this experiment and the new beta entry control is not known.\n\n**What**\n\nClaude Code now looks up a remote experiment setting named `tengu_curried_trinket`. An experiment setting is a value the server sends to decide which version of a feature an account gets. The name existed before, and it now appears in two more lists of settings Claude Code checks. If the server sends nothing, it falls back to `control`, the usual name for the unchanged version.\n\nA new entry was also added to the list of beta features Claude Code can ask the API for. Beta features are API capabilities that are still being tested. This one is requested only when a certain condition holds.\n\n**Why**\n\nThis looks like an experiment being prepared. It changes nothing you can see until it is used.\n\n- Flag `tengu_curried_trinket`: Not enough to say (read for one account on one subscription tier against v2.1.318; 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: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}