githubEdit

databaseConversation Stores

Learn how conversations are persisted and managed across different storage backends.

Overview

Conversation stores determine how agent conversations are saved, loaded, and managed. AI Dev Kit supports multiple storage backends:

  • None - No persistence (in-memory only)

  • LocalFile - Local file system storage

  • ThreadsApi - OpenAI Threads API

  • RealtimeApi - OpenAI Realtime API

  • ConversationsApi - OpenAI Conversations API

  • Custom - Your own storage implementation

ConversationStoreType

public enum ConversationStoreType
{
    None,                  // Do not save
    LocalFile,             // Local file storage
    ThreadsApi,            // OpenAI Threads API
    RealtimeApi,           // OpenAI Realtime API
    ConversationsApi,      // OpenAI Conversations API
    Custom,                // Custom storage implementation
}

Store Implementations

IConversationStore Interface

All stores implement this interface:

ConversationPersistMode

Controls how conversation items are persisted:


Built-in Stores

1. NoopConversationStore (None)

No persistence - conversations exist only in memory.

When to use:

  • Testing and development

  • Temporary conversations

  • When you don't need history

Configuration:

Behavior:

  • All operations return null or empty results

  • No data is saved to disk or API

  • Conversations are lost when agent is disposed


2. LocalFileStore

Saves conversations to local JSON files.

When to use:

  • Desktop applications

  • Single-device storage

  • Offline-first apps

  • Development and testing

Configuration:

File Structure:

Features:

  • Fast local access

  • Works offline

  • No API costs

  • Cross-session persistence

Limitations:

  • Not synchronized across devices

  • Manual backup required

  • No multi-user support

Example:


3. ThreadsApiStore

Uses OpenAI's Threads API for conversation storage.

When to use:

  • When using OpenAI Assistants API

  • Multi-device synchronization needed

  • Cloud-based conversation history

  • Collaborative conversations

Configuration:

Features:

  • Cloud synchronization

  • Multi-device access

  • OpenAI manages storage

  • Built-in message management

Limitations:

  • Requires OpenAI API key

  • API costs apply

  • Requires internet connection

  • Only works with Assistants API

Example:


4. ConversationsApiStore

Uses OpenAI's Conversations API (Responses API).

When to use:

  • When using OpenAI Responses API

  • Modern conversation management

  • Delta-based updates

  • Efficient storage

Configuration:

Features:

  • Efficient delta updates

  • Cloud synchronization

  • Metadata support

  • Item-level operations

Implementation:

Example:


5. RealtimeApiStore

Storage for OpenAI Realtime API conversations.

When to use:

  • Voice-based conversations

  • Real-time audio interactions

  • Low-latency applications

Configuration:


Custom Store Implementation

Create your own storage backend by implementing IConversationStore.

Example: Cloud Storage

Usage:


Store Selection Guide

Store Type
Best For
Pros
Cons

None

Testing, temporary chats

Fast, no setup

No persistence

LocalFile

Desktop apps, offline

Fast, offline, free

No sync, single device

ThreadsApi

Assistants API, cloud sync

Multi-device, managed

Requires OpenAI, costs

ConversationsApi

Responses API, modern apps

Efficient, managed

Requires OpenAI, costs

RealtimeApi

Voice conversations

Real-time, low latency

Requires OpenAI, costs

Custom

Specific requirements

Full control

Implementation effort


Persist Modes

Only new items are saved to storage:

Advantages:

  • Most efficient

  • Minimal API calls

  • Faster saves

  • Reduced bandwidth

Works for:

  • Append-only conversations

  • Most use cases

FullSnapshot

Entire conversation is saved on every update:

Advantages:

  • Complete state preservation

  • Handles edits/deletions

  • Simpler consistency model

Disadvantages:

  • More API calls

  • Higher costs

  • Slower for large conversations

When to use:

  • Conversations with edits

  • Item deletions

  • Complex state management


Best Practices

✅ Do

❌ Don't


Migration Between Stores

To migrate conversations between stores:


Next Steps

Last updated