Claude API Message Threads: Stop Resending the Whole Conversation — Explained Honestly

If you have ever built a long-running agent on the Claude Messages API, you know the tax. Every turn, your app resends the entire conversation — every earlier message, every tool result, the whole history — just to ask the next question. The longer the session runs, the heavier each request gets, and the longer the user waits for the first token.

Anthropic opened a way around that on 2 November 2026: Message Threads, now in public beta on the Claude Messages API. The idea is simple enough to explain in one sentence — the API keeps the conversation on its side, so later requests send only what is new — but the details matter, because this is a beta with real limits, and one popular misunderstanding needs clearing up straight away: it does not cut your token bill.

What it is

Message Threads lets a Messages API application hand conversation state to Anthropic's servers between turns. The first request — the "create" request — sends the full conversation, including the system prompt and tools, together with the `thread` parameter, and starts a thread. The API stores the conversation and Claude's reply under that response's ID.

Every later turn — a "continue" request — sends only the messages since the previous response, plus that previous response's ID. The API reconstructs the rest before calling the model. In code terms, you add the `thread` parameter and the `message-threads-2026-08-12` beta header; the official SDKs provide a thread helper that handles the header, keeps the conversation in memory, and replays the full conversation once for certain continuation errors.

Anthropic pitches it at exactly the workloads where resending hurts most: long-running coding agents, computer-use agents whose screenshots stay with the thread, and document- and image-heavy workflows. It is already on by default for most Claude Code users, which is where the headline numbers come from.

What Anthropic claims — and what it does not claim

The vendor numbers, attributed to Anthropic and not presented as our own tests:

• On requests of 500,000 to 1 million tokens, median time to first token is about 35% lower with message threads, based on the Claude Code rollout.
• In long conversations, median request size fell from about 800 KB to 1.8 KB.

Both are Anthropic's figures from its own rollout. We have not tested Message Threads hands-on, and no independent benchmark is cited here, so treat them as the vendor's claims, not verified results.

And here is the part worth saying plainly, because it is easy to get wrong: **Claude still reads the full conversation on every turn.** Token usage, token charges and rate limits are unchanged. What you save is upload time and request size — the waiting, not the bill. Prompt caching, for the record, still needs to be requested explicitly; threads do not switch it on for you.

Where it is available

Beta support is on every model, and the feature is available on:

• The native Claude Platform
• Claude Platform on AWS