Skip to main content
Retired: The Chat and Message API was retired on 21 August 2026, and the endpoints described below no longer exist. This guide is kept for reference while integrations migrate.New projects should use Direct Responses if the app owns safety, or the guarded Responses API for built-in guardrails and tradition. If you need model-family selection, auto-routing, or grounded completions, use Completions V2. Existing integrations should migrate as soon as possible.View Migration Guide →
For conversational AI, Chat Threads are the structure behind persistent assistants. Think of them like ChatGPT’s conversations: stored, contextual, and evolving.

What is a Chat Thread?

A thread is a persistent conversation made up of messages between a user and an assistant. It carries memory, intent, context, and relationship, not just history.
Instead of building state management yourself, a chat-native model and API give you this behavior out of the box.

Why Threads Are a Game-Changer

Built-in Context History

Threads preserve the full message history by default, so:
  • No need to re-send long prompts each time.
  • Context-aware responses feel more helpful and consistent.
  • It supports multi-turn reasoning and corrections (e.g., “Actually, I meant…”).
  • You get session persistence without writing session logic.

First-Class RAG (Retrieval-Augmented Generation)

Threads pair naturally with RAG systems by grounding responses on:
  • Domain-specific docs
  • Internal knowledge bases
  • External APIs or tools
Chat threads can be augmented with value-aligned sources that ensure responses stay on-brand, accurate, and compliant.

Immediate Access to Proprietary Features

The “Chat” object gives you production-ready features without building your own conversation manager:

Aligns with Real User Mental Models

People don’t talk to AI one prompt at a time. They:
  • Ask follow-ups
  • Refer back to previous context
  • Expect the AI to “remember”
Threads let your app feel human, collaborative, and intelligent—not transactional.

Foundation for Personalization and Long-Term Memory

Chat threads create a structured, queryable history you can use to personalize future sessions or build product analytics around AI interactions.

TL;DR: Why Use Chat Threads?

Whether you’re building support bots, copilots, or AI apps, threads save you from managing conversation infrastructure yourself.

Next steps

Without threads, your app holds the conversation history itself: Conversations and Context Windows covers storing and trimming it. The retired Chat tutorial is kept for reference.

Migrate to Completions V2

Move from Chat threads to the Completions V2 API.

Completions V2

The current API for conversational AI.