AI Catchup

Claude Opens Message Threads in the Messages API Public Beta

By 2 min read

Anthropic's public beta for Message Threads lets developers send only new messages to an existing Messages API conversation instead of resending its full history. Threads are held encrypted in memory for five minutes after the last request. The feature does not reduce token usage, and Anthropic reports a median time-to-first-token improvement for long-context Claude Code requests.

Anthropic has opened Message Threads as a public beta in the Messages API. A client can continue a conversation by sending only new messages and the ID of the previous response, rather than resending the full history on every turn. (Anthropic's announcement)

How Message Threads Work

The first request includes the conversation and starts a thread with the thread parameter. Later requests include only new messages and the previous response ID. Anthropic holds each thread in encrypted server memory between turns and does not write it to disk. (Anthropic's announcement)

A thread expires five minutes after its last request. When that happens, the client resends the full conversation to start a new thread. (Anthropic's announcement)

Latency and Token Usage

Anthropic reports that Claude Code requests with 500k to 1M tokens saw about a 35% drop in median time to first token (TTFT) with message threads. (Anthropic's announcement)

Sending smaller requests does not cut token usage: Anthropic says Claude still reads the full conversation on every turn, so token usage stays the same. The client sends less repeated data, while Claude can start responding sooner. (Anthropic's announcement)

Availability and Best-Fit Workflows

The public beta is available on the native Claude Platform, Claude Platform on AWS, Claude in Microsoft Foundry, and Claude Models on Google Cloud (Anthropic managed). Standard Claude token rates and existing rate limits apply. (Anthropic's announcement)

Anthropic highlights long-running coding agents, computer-use agents, and document- or image-heavy workflows as good fits when latency matters. The feature is aimed at long-running sessions where conversation history grows across repeated turns. (Anthropic's announcement)

Related coverage

Sources

Frequently Asked Questions

What are Claude API message threads?

They let a client continue a Messages API conversation by sending only new messages and the ID of the previous response, rather than resending the full conversation history.

How long does a message thread stay active?

Anthropic keeps thread state in encrypted memory for five minutes after the last request. After that, the client can resend the full conversation to start a new thread.

Do message threads reduce Claude token usage?

No. Anthropic says Claude still reads the full conversation on each turn, so token usage stays the same even though each request is smaller.

Get the weekly AI Catchup

Tools, practices, and what matters, in your inbox every week.