cd /news/ai-agents/make-long-running-agents-faster-with… · home › topics › ai-agents › article
[ARTICLE · art-162744] src=claude.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

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.

read2 min views1 publishedNov 2, 2026
Make long-running agents faster with message threads
Image: source

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 to get started.

── more in #ai-agents 4 stories · sorted by recency
── more on @anthropic 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/make-long-running-ag…] indexed:0 read:2min 2026-11-02 · —