Unverified50% confidenceFactExact time
In regular Claude API calls, each POST /v1/messages must carry the complete messages array, and the server does not remember prior turns.
1
Sources
50%
Confidence
Long-term
Relevance
11/3/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedClaude Code v2.1.300's local session record now saves the system prompt, tools and parameters of each API request, facilitating full request reproduction.72% similarUnverifiedThe 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.71% similarUnverifiedMainstream large-model APIs bill by input tokens and do not retain server-side session state, causing the same log segment to be counted as input tokens again in subsequent turns.70% similarUnverifiedAnthropic's Claude API supports assistant prefill, implemented by setting the role of the last message in the messages array to assistant with no stop_reason.69% similarUnverifiedMany modern APIs use an asynchronous processing architecture where write requests first enter a message queue, the server returns 200 to confirm the request has been queued, and the actual persistent write is completed asynchronously in the background—a phenomenon known as eventual consistency.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1128830API
curl https://kongchang.com/api/v1/knowledge/claims/1128830MCP
get_claim(id=1128830)