{"version":"2.1.288","anchor":"remote-session-channel-ui-surface-frames-are-now-judged-aga","canonical_anchor":"remote-session-channel-ui-surface-frames-are-now-judged-aga","heading":"Interface messages in remote sessions now face the same sender check as hooks and plugins","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-session-channel-ui-surface-frames-are-now-judged-aga","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Interface messages in remote sessions now face the same sender check as hooks and plugins\n\nMessages that update the on-screen interface in a remote session are now checked against the minimum trust level for their sender\n\n**Unclear.** It is unclear what happens to genuine interface messages that arrive without proof of who sent them.\n\n**What**\n\nIn a remote session, messages arrive over a channel between Claude Code and the service hosting it. Some of those messages change what you see on screen. Claude Code now checks these interface messages against the channel's minimum trust requirement for the sender, the same check it already ran for messages from hooks and plugins. Before, interface messages were not in the guarded group, and the check also depended on one more condition that has now been dropped.\n\n**Why**\n\nThis tightens security for screen updates that come in from outside during a remote session, so an unverified sender has a harder time changing what is displayed.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}