{"version":"2.1.301","anchor":"bridge-remote-session-exposes-reportinternalmetadata-and-wor","canonical_anchor":"bridge-remote-session-exposes-reportinternalmetadata-and-wor","heading":"Remote Control sessions can report internal details to the app hosting them","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/bridge-remote-session-exposes-reportinternalmetadata-and-wor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Remote Control sessions can report internal details to the app hosting them\n\nRemote Control sessions now let the hosting app send internal details and read the session ID with the worker's connection number\n\n**What**\n\nRemote Control lets you follow and steer a Claude Code session from another device. Its connection to the app hosting the session gains two abilities:\n\n- Reporting internal details about the session\n\n- Giving the session ID together with the current connection number of the worker running it\n\nBoth are blocked once the session has passed to a different owner.\n\n**Why**\n\nThe app hosting a Remote Control session can now pass along internal details about it.\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.301; 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- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}