{"version":"2.1.290","anchor":"surface-request-refusals-and-session-writers-freshness-check","canonical_anchor":"surface-request-refusals-and-session-writers-freshness-check","heading":"Remote sessions now refuse some interface requests from less trusted clients","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/surface-request-refusals-and-session-writers-freshness-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote sessions now refuse some interface requests from less trusted clients\n\nRemote sessions refuse interface requests from clients below a trust level, or when the policy or the list of who may write is unreadable or stale\n\n**Unclear.** Whether these checks always apply or only under a policy is not known.\n\n**What**\n\nIn remote sessions, a connected client can ask Claude Code to show parts of an interface. Claude Code now handles these requests more strictly:\n\n- Requests from clients below a minimum attestation level, meaning proof of what the client is, are refused\n\n- An unreadable policy counts as a refusal\n\n- Some requests are dropped when the record of who may write to the session is out of date\n\nRefused requests are answered as not served.\n\n**Why**\n\nThis tightens which remote clients Claude Code trusts to put things on screen.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}