A shorter way to continue a conversation
Anthropic’s November 2 release notes introduce beta message threads for the Messages API. An API lets software services exchange requests and responses. A thread keeps conversation context on the server, so an app can send just the next messages. [1]
Plan for pauses and privacy requirements
Threads are best-effort: they expire five minutes after the last request and are deleted within an hour of last use. Keep the conversation in your app so it can resend it when continuation fails. Pricing and rate limits are unchanged. [2]
The beta temporarily holds conversation data, so Anthropic excludes it from its zero-data-retention option. It is also ineligible for HIPAA readiness, the service’s arrangements for handling protected US health information. Review your service’s data requirements before enabling it. [2]
Our take
Imagine a small shop’s assistant helping with a fictional damaged-order report. A customer pauses to find an order number. The next message should continue reliably or rebuild the conversation from the app’s saved copy. A dropped thread should not make the customer repeat everything.
Ask the developer to check a long pause, an app restart, and a failed continuation using made-up details before switching it on. Include a clear explanation of where the conversation is stored. We have not called this API or measured a speed gain.