Anthropic’s November 2, 2026 release notes announce message threads in beta for the Messages API, using the message-threads-2026-08-12 header. The server reconstructs the conversation, allowing later turns to send new messages and the previous response ID instead of resending the full history. Official source.
Shorter transport does not replace your transcript
The release notes describe smaller requests and lower time to first token. Those are not measured improvements for your application, nor proof that all prior context becomes free. The documentation says your application remains the source of truth and should keep every message.
Build recovery before rolling out
- Store the complete conversation in your application and retain the response ID needed for the next turn.
- Handle thread expiry: after a 404 indicating it cannot continue, create a new thread by replaying the complete history. The SDK helper can handle replay, but its local transcript exists only in memory.
- Compare request size, first-token latency and reported usage on your own workload, including recovery after an idle pause or process restart.
Expiry and privacy conditions
A thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use. The feature documentation marks message threads as not eligible for Zero Data Retention or HIPAA. Teams with such requirements should verify applicability before enabling it. Only a source date, not an exact publication time, was available.
Sources and method
Official source · Related documentation
Prepared with AI assistance from official materials, checked on November 6, 2026. No hands-on test was performed. The checks suggested above are editorial recommendations.
