{"version":"2.1.323","anchor":"tether-threads-can-be-held-stateless-after-a-refusal-retry","canonical_anchor":"tether-threads-can-be-held-stateless-after-a-refusal-retry","heading":"Message threads switch to stateless requests after a refusal retry","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tether-threads-can-be-held-stateless-after-a-refusal-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Message threads switch to stateless requests after a refusal retry\n\nAfter a retry that followed a refusal, Claude Code can now send turns as stateless requests instead of continuing the stored thread\n\n**What**\n\nThere is one more case where Claude Code stops continuing a conversation thread stored on the server: after a retry that followed a refusal, the thread can be held in stateless mode. Stateless means each request carries the conversation itself rather than pointing at the stored thread. This case is also recorded in the telemetry Claude Code sends about these threads.\n\n**Why**\n\nThis changes when Claude Code keeps using the thread stored on the server.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}