Make long-running agents faster with message threads

Anthropic released message threads in public beta on the Claude Platform, letting agents send only new messages and the previous response ID each turn instead of resending full conversation history. With message threads on by default for most Claude Code users, requests of 500k to 1M tokens saw median time to first token drop by about 35%, Anthropic said. Threads are held encrypted in memory, expire 5 minutes after the last request, and do not reduce token usage because Claude still reads the full conversation each turn.

Make long-running agents faster with message threads New in the Messages API, send your conversation once, and the API receives only what’s new with every turn. Message threads is now available in public beta on the Claude Platform. With message threads, agents no longer need to resend the full conversation history on every turn, reducing latency for long-running sessions. How message threads works A coding agent might make hundreds of requests in one session, and each request resends every earlier message and tool result. Once a conversation reaches hundreds of thousands of tokens, resending all of it adds time before Claude starts responding. With message threads, agents send only what’s new since the last turn, which reduces time to first token TTFT . With message threads on by default for most Claude Code users, requests with 500k to 1M tokens see median TTFT drop by about 35%. To use message threads, add the thread parameter to Messages API requests. The first request includes the full conversation and starts a thread. Each request after that includes only the new messages and the ID of the previous response. Between turns, we hold each thread in memory, where it’s encrypted and not written to disk. A thread expires 5 minutes after its last request and your client then resends the full conversation to start a new one. While each request is smaller with message threads, Claude still reads the full conversation on every turn, so token usage stays the same. Message threads is best for active sessions where latency matters, including: - Long-running coding agents , where each tool result or file edit adds to the conversation. - Computer use agents , where screenshots stay with the thread instead of being re-uploaded on every turn. - Document and image-heavy workflows , where requests are made smaller. The more context an agent carries, the more message threads can reduce time to first token. Getting started Message threads is available now in public beta on the native Claude Platform, and on Claude Platform on AWS, Claude in Microsoft Foundry, and on Claude Models on Google Cloud Anthropic managed . Standard Claude token rates and existing rate limits apply. See the documentation http://platform.claude.com/docs/en/build-with-claude/message-threads to get started.