{"version":"2.1.299","anchor":"liveness-enforced-preview-tunnel-reconnect-condition-changed","canonical_anchor":"liveness-enforced-preview-tunnel-reconnect-condition-changed","heading":"Quiet preview connections are forced to reconnect under a different rule","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/liveness-enforced-preview-tunnel-reconnect-condition-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Quiet preview connections are forced to reconnect under a different rule\n\nThe number of unanswered checks before a quiet preview connection is forcibly reconnected now grows with the time that has passed\n\n**What**\n\nClaude Code checks that its preview connection is still alive by sending regular checks. When enough checks go unanswered, it forces the connection to reconnect. The rule for that has changed. Before, a set number of quiet checks within a time window triggered it. Now the number needed is the larger of that set number and a count that grows with the time that has passed.\n\n**Why**\n\nThis changes when a quiet preview connection is cut and reopened.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}