{"version":"2.1.281","anchor":"message-threads-tether-new-creditretrystateless-forces-a","canonical_anchor":"message-threads-tether-new-creditretrystateless-forces-a","heading":"Message-threads (tether): new creditRetryStateless forces a stateless request","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/message-threads-tether-new-creditretrystateless-forces-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Message-threads (tether): new creditRetryStateless forces a stateless request\n\nA new creditRetryStateless input makes the thread planner send a turn as a fresh stateless request instead of continuing a server-side thread\n\n**Unclear.** The finding does not say what sets `creditRetryStateless`.\n\n**What**\n\nThe planner that decides whether a turn continues an existing server-side message thread has a new input, `creditRetryStateless`. When it is set, the planner does not continue the thread. The request is sent stateless instead, meaning it carries the conversation itself rather than pointing at a thread stored on the server.\n\nThis joins the other situations that already force a stateless request: holds from the model, relay, classifier and drop paths. The new value is also recorded on the `tengu_tether_live_outcome` telemetry event.\n\n**Why**\n\nThis adds one more case where Claude Code falls back to a plain stateless request. Nothing changes in what you type or see. The difference is in how the turn is sent to the server."}