Frame publish context is now permanently off and no server setting can enable it.
tengu_frame_publish_context Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
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?
This path was previously behind the tengu_frame_publish_context remote flag, off unless Anthropic's config enabled it. The flag lookup is gone and the check now returns false unconditionally; the flag name no longer appears anywhere in the build, so no server value can switch it on.
return K("tengu_frame_publish_context", !1);
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Org public-projects memory kind dropped
Both mention config
-
v2.1.239
Remote Control bridge sessions reject foreign --mcp-config entries
Both mention config
-
v2.1.239
Remote sessions drop disallowed --mcp-config servers instead of failing the run
Both mention config