创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Anthropic推出Claude消息线程

AI 总结

Anthropic为Claude Messages API推出消息线程公开测试版,智能体首次发送完整对话后,后续只需提交新增消息和上一响应ID。Anthropic称,对于50万至100万令牌的请求,首个令牌生成时间中位数下降约35%,但令牌用量、价格和现有速率限制不变。线程在内存中加密保存,最后一次请求五分钟后过期,并已为多数Claude Code用户默认启用。

深度见解

这项API改动可降低长时间运行智能体的请求延迟,但约35%的改善数据仅为厂商声明,所供报道未提供独立测量。

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.

#Anthropic#Claude#Claude Messages API#Claude Code#AWS#Microsoft Foundry#Google Cloud

原文约 2 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。