{"version":"2.1.286","anchor":"tether-threads-presumed-expired-after-idle-lifetime-new-cre","canonical_anchor":"tether-threads-presumed-expired-after-idle-lifetime-new-cre","heading":"Long-idle tether threads start fresh instead of continuing","tier":"notice","area":"Tether","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/tether-threads-presumed-expired-after-idle-lifetime-new-cre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Long-idle tether threads start fresh instead of continuing\n\nIf a tether thread has been idle as long as the server keeps it, Claude Code now starts a new thread rather than continuing the old one\n\n**Unclear.** Whether the tether feature is in use for readers is not known.\n\n**What**\n\nIn Claude Code's tether feature, a thread that has been idle for at least as long as the server keeps it alive is now treated as expired. Claude Code sends a request to create a new thread instead of continuing the old one, and logs the reason. Before, it continued the thread whenever its starting point was still valid.\n\n**Why**\n\nOn sessions left idle for a long time, this avoids replays that the server would reject because the old thread no longer exists.\n\n- Area: Tether\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}