{"version":"2.1.323","anchor":"cloud-shell-tunnel-can-answer-relayed-requests-in-process","canonical_anchor":"cloud-shell-tunnel-can-answer-relayed-requests-in-process","heading":"Cloud session preview tunnel can answer tool server requests directly","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/cloud-shell-tunnel-can-answer-relayed-requests-in-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Cloud session preview tunnel can answer tool server requests directly\n\nIn cloud sessions, the preview tunnel can now answer tool server requests inside Claude Code and relays only checked POST, GET and DELETE requests\n\n**What**\n\nIn cloud sessions, a preview tunnel passes requests from tool servers through to Claude Code. It used to send every such request over a local network connection. It can now answer them inside Claude Code's own process instead.\n\n- The stream of data it sends back is now throttled, so it goes out at a limited rate.\n\n- A new relay step checks each request's method, headers and path. Only POST, GET and DELETE are relayed, and paths with unescaped characters are refused.\n\n**Why**\n\nThis is behind-the-scenes plumbing for cloud sessions, and requests that fail the new checks are not passed on.\n\n- Flag `tengu_cloud_session_shell`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, 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: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}