{"version":"2.1.280","anchor":"rich-remote-control-action-details-stay-off-by-default","canonical_anchor":"rich-remote-control-action-details-stay-off-by-default","heading":"Rich remote-control action details stay off by default","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/rich-remote-control-action-details-stay-off-by-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Rich remote-control action details stay off by default\n\nA gate controls whether remote-control approval requests include compact action details like the raw command\n\n**What**\n\nWhen you approve or respond to an action from a cloud or companion session (a Claude Code session running remotely rather than on your machine), Claude Code sends a control request back asking whether a tool can be used, or asking you to respond to a dialog. Claude Code can now attach a compact summary to that request, called `requires_action` details, including things like the tool's display name, a short description of the action, and the raw command being run, instead of forwarding only the raw request. Whether this summary is built and sent is controlled by a setting named `tengu_bridge_requires_action_details`.\n\n**Why**\n\nWhen active, this should make it easier to see at a glance what a remote session is asking permission to do, without having to parse the raw request yourself.\n\n- Flag `tengu_bridge_requires_action_details`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.280; this account: on, anonymous baseline: on, 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: Remote Control\n- Names: `tengu_bridge_requires_action_details`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}