// AI Platform Drift

Messages API adds server-side conversation threads in beta

Claude Platform release notes · published 2026-11-11 04:53 UTC
WORTH KNOWING VERIFY_ONLY API
WHAT CHANGEDThe Messages API now supports message threads via the message-threads-2026-08-12 beta header. Threads keep conversation state on the server, allowing subsequent requests to send only new messages instead of the full history. Threads expire 5 minutes after the last request and are deleted within 1 hour of last use. Available on Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.
WHY IT MATTERSRequest payload size decreases for multi-turn conversations, reducing time to first token. Conversation state now lives server-side with automatic expiration, changing data retention characteristics from client-controlled to time-bounded server storage.
WHAT TO DOReview whether your application's conversation patterns fit the 5-minute idle and 1-hour maximum retention windows. Test the message-threads-2026-08-12 beta header on a non-production workload to measure latency and payload size changes before adopting.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — November 2, 2026
+https://platform.claude.com/docs/en/release-notes/overview#november-2-2026
+Mon, 02 Nov 2026 00:00:00 GMT
+
+Long conversations and agent loops on the Messages API can now send smaller requests and get a lower time to first token with message threads, in beta with the message-threads-2026-08-12 beta header. The API keeps the conversation on the server, so each later request sends only the new messages. A thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use. Message threads are available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew API feature with defined beta header, server-side state management, and explicit retention policy affects integration patterns.
signalsnew feature announcement with beta header identifier · API behavior change: conversation state now server-side · new retention/expiration terms: 5 min idle, 1 hour max · availability across multiple deployment platforms · impacts request payload size and latency characteristics
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)