Anthropic has put message threads on its Messages API into public beta, letting developers continue a conversation by sending only new messages and the ID of the previous message rather than resending the full history.
Public beta · Anthropic
Messages API threads move conversation history to the server
Developers can continue a conversation by sending only the new messages and the ID of the previous message, instead of resending the full history on every turn.
Public beta
Available now, but may change before general release.
New messages + ID
Each request carries only the latest turn and a reference to the prior message.
Not yet published
Latency figures, pricing, and thread retention periods.
How each turn is sent
Qualitative flow only. The announcement gives no size or timing measurements.
Conventional: full history every turn
Client stores history
→
Resend all prior messages + new message
→
Model replies
Threads: server holds the conversation
Send new messages + previous message ID
→
Server retrieves stored thread
→
Model replies sooner, per Anthropic
Upside for builders
The client no longer has to resend the whole exchange each turn.
History tracking shifts to the platform.
Suited to chat assistants, coding tools, and agent workflows.
Open questions
No specific latency numbers have been published.
Pricing and how long threads are retained are not detailed.
Interaction with other Messages API functions is unspecified.
No independent assessment of performance exists yet.
The bigger shift
Model providers are taking on more conversation state, reducing what application developers must manage.
Chat assistants
Coding tools
Agent workflows
Continue reading The rest of this article is for AI News Blitz readers. Choose an option below to keep reading.
Already purchased? Sign in ✓ Signed in — this article isn’t included in your current plan.Unlocking the full article...