A chat relay flag no longer does anything; entrypoint alone decides that path.
tengu_retire_chat_relay_artifact_backstop On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The flag tengu_retire_chat_relay_artifact_backstop no longer affects anything; the check that consulted it was removed. Whether the backstop path runs is now decided only by the entrypoint, such as claude-code-github-action or mcp.
tengu_retire_chat_relay_artifact_backstop
Strings lifted out of the shipped bundle, so the claim above can be checked against them.