[KongchangAI]
Product消息线程

Message Threads

A beta feature of the Anthropic Claude API that retains multi-turn conversation state on the server for a short period, so the client only needs to send newly added messages each turn, reducing retransmitted tokens and bandwidth.

Timeline (last 90 days)

Nov 10

Anthropic launched Message Threads, which keeps conversation history on the server side so that new requests transmit only increments; the company says it does not save tokens but does speed things up, and it is enabled by default in Claude Code.

Unverified50%
Nov 4

Anthropic launched the Message Threads feature for the Messages API, in which agents only need to send the changed parts, shortening time to first token by about 35% in requests of 500,000 to 1 million tokens, released as a public test.

Unverified50%
Nov 3

The message threads beta feature provides SDK helper methods that encapsulate thread creation and continuation logic, so developers do not need to manually manage thread IDs or concatenate message arrays.

Unverified50%
Nov 3

When the TTL of message threads' server-side state expires, it silently becomes invalid, and the server does not proactively notify the client.

Unverified50%
Nov 3

The Claude API introduced a beta feature called "Message Threads" that allows clients to send only new messages in multi-turn conversations, with conversation state retained on the server side.

Unverified50%
Nov 3

For scenarios requiring strictly reproducible and auditable conversation records, using message threads with server-held state introduces additional debugging and auditing considerations.

Unverified50%
Nov 3

Message threads are best suited to multi-turn, short-interval, long-context conversational applications, and are not suited to sessions that stay suspended for long periods.

Unverified50%
Nov 3

The server-side thread state for the Message Threads feature is retained for 5 minutes, after which the thread may become invalid.

Unverified50%

All Facts (8)

Unverified

For scenarios requiring strictly reproducible and auditable conversation records, using message threads with server-held state introduces additional debugging and auditing considerations.

50%
Unverified

The server-side thread state for the Message Threads feature is retained for 5 minutes, after which the thread may become invalid.

50%
Unverified

The message threads beta feature provides SDK helper methods that encapsulate thread creation and continuation logic, so developers do not need to manually manage thread IDs or concatenate message arrays.

50%
Unverified

When the TTL of message threads' server-side state expires, it silently becomes invalid, and the server does not proactively notify the client.

50%
Unverified

Message threads are best suited to multi-turn, short-interval, long-context conversational applications, and are not suited to sessions that stay suspended for long periods.

50%
Unverified

Anthropic launched Message Threads, which keeps conversation history on the server side so that new requests transmit only increments; the company says it does not save tokens but does speed things up, and it is enabled by default in Claude Code.

50%
Unverified

Anthropic launched the Message Threads feature for the Messages API, in which agents only need to send the changed parts, shortening time to first token by about 35% in requests of 500,000 to 1 million tokens, released as a public test.

50%
Unverified

The Claude API introduced a beta feature called "Message Threads" that allows clients to send only new messages in multi-turn conversations, with conversation state retained on the server side.

50%

Source Articles