{"version":"2.1.317","anchor":"widget-tool-states-and-mcp-app-widget-context-gate-tengu-am","canonical_anchor":"widget-tool-states-and-mcp-app-widget-context-gate-tengu-am","heading":"Cloud workers can keep widget state that arrives with a message","tier":"internal","area":"MCP Apps","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/widget-tool-states-and-mcp-app-widget-context-gate-tengu-am","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Cloud workers can keep widget state that arrives with a message\n\nBehind a server-side switch, Claude Code running headless in the cloud keeps up to 256 tool states, or 1 MiB, sent along with a message\n\n**What**\n\nClaude Code can run as a headless cloud worker: a copy running on a server with no screen of its own, driven by another app. A new server-side switch now controls what is called widget context there. Widgets are interactive pieces, such as those from MCP Apps, whose state the driving app can send along. With the switch on, the tool states that arrive with a message are kept, up to 256 states or 1 MiB in total.\n\nThe worker also sends its worker epoch value when either this switch or a related one is on. The message format gains fields for the host's tool interface and for the path of synced skills.\n\n**Why**\n\nIt gives the app that drives a cloud session a way to hand the state of its widgets over to Claude Code.\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.317; this account: off, anonymous baseline: off, compiled default: off) 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: MCP Apps\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}