{"version":"2.1.323","anchor":"widget-bare-tool-names-rewritten-behind-tengu-generic-ember","canonical_anchor":"widget-bare-tool-names-rewritten-behind-tengu-generic-ember","heading":"Remote sessions can fix widget tool calls that leave off the tool's prefix","tier":"soon","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/widget-bare-tool-names-rewritten-behind-tengu-generic-ember","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote sessions can fix widget tool calls that leave off the tool's prefix\n\nIn remote sessions, a widget tool called by its short name can be matched to its full name, behind a remotely controlled switch\n\n**What**\n\nIn remote sessions, which are sessions where `CLAUDE_CODE_REMOTE` is set, Claude sometimes calls a widget tool by its short name. Widget tools come from connectors and normally carry a prefix. If no tool has that short name but a prefixed widget tool matches it, Claude Code now rewrites the call to use the full tool name and records that it did so.\n\nThis only happens when a remotely controlled switch is on. In readings so far, the server returned it off both for this site's account and for an anonymous check.\n\n**Why**\n\nIt affects how widget tool calls are handled in remote sessions, and stays dormant unless the switch is turned on.\n\n- Flag `tengu_generic_ember`: Off in both readings (read for one account on one subscription tier against v2.1.323; 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: Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}