{"version":"2.1.284","anchor":"tether-stateless-threading-gets-a-toolresultclearingheldstat","canonical_anchor":"tether-stateless-threading-gets-a-toolresultclearingheldstat","heading":"Clearing old tool results now makes Claude Code send a fresh stateless request","tier":"internal","area":"Context Management","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/tether-stateless-threading-gets-a-toolresultclearingheldstat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Clearing old tool results now makes Claude Code send a fresh stateless request\n\nWhen tool-result clearing is active, the thread planner sends the turn as a fresh stateless request instead of continuing a server-side thread\n\n**What**\n\nThe planner that decides whether a turn continues a message thread stored on the server has a new input, `toolResultClearingHeldStateless`. It is set when tool-result clearing is active, meaning Claude Code has removed older tool outputs from the conversation. When it is set, the turn is not sent as a thread continuation. It is sent stateless instead, carrying the conversation itself rather than pointing at the thread on the server. The new value is also recorded in the planner's telemetry.\n\n**Why**\n\nOnce Claude Code has cleared tool results on your side, the server's stored thread no longer matches your conversation. Sending a fresh request keeps the two from getting out of step.\n\n- Area: Context Management\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}