{"version":"2.1.318","anchor":"tunnel-websocket-data-moved-from-base64-strings-to-bytespro","canonical_anchor":"tunnel-websocket-data-moved-from-base64-strings-to-bytespro","heading":"The preview tunnel now sends data as raw bytes instead of text","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/tunnel-websocket-data-moved-from-base64-strings-to-bytespro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### The preview tunnel now sends data as raw bytes instead of text\n\nThe preview tunnel now accepts requests as text or binary, passes connection data as raw bytes instead of base64 text, and drops malformed requests\n\n**What**\n\nClaude Code's preview tunnel is the connection it uses to forward preview traffic. It changed how it carries data:\n\n- requests can arrive either as text or in a compact binary format (protobuf)\n\n- data on live connections is passed as raw bytes; previously it was converted to base64, a way of writing binary data as plain text\n\n- a binary request that cannot be decoded is dropped, with a message saying so\n\n**Why**\n\nThis is a change to the format of data on the preview tunnel. It does not change anything you do directly, but a request in a broken format is now dropped and reported rather than processed.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}