SQLite Persistence

SQLite saves agent conversations to a local .db file — no external database required.

from praisonaiagents import Agent, MemoryConfig
from praisonaiagents import db

agent = Agent(
    name="Assistant",
    instructions="You are a helpful assistant.",
    memory=MemoryConfig(
        db=db(database_url="sqlite:///conversations.db"),
        session_id="dev-session",
    ))
agent.start("Hello — saved to SQLite")

The user develops locally; SQLite writes conversations to a single file on disk.

Quick Start

Simple Usage

from praisonaiagents import Agent, MemoryConfig
from praisonaiagents import db

agent = Agent(
    name="Assistant",
    memory=MemoryConfig(
        db=db(database_url="sqlite:///conversations.db"),
        session_id="session-1",
    ))
agent.start("Remember my favourite colour is blue")

With Configuration

Choose sync or async when using the factory directly:

from praisonai.persistence.factory import create_conversation_store

# Sync — scripts and multi-threaded agents
store = create_conversation_store(
    "sqlite",
    path="./conversations.db",
    mode="sync",
)

# Async — FastAPI / asyncio apps
store = create_conversation_store(
    "sqlite",
    path="./conversations.db",
    mode="async",
)

Before PR #1763, AsyncSQLiteConversationStore exposed sync wrappers callable from regular functions. Those wrappers were removed — use mode="sync" (sync_sqlite backend) when calling from sync code.

How It Works

Connections go through the hardened sqlite_connect factory, which prefers WAL and falls back to DELETE on network and container filesystems.

Table	Purpose
`sessions`	Session metadata
`messages`	User and agent messages
`runs`	Agent execution runs
`tool_calls`	Tool usage records

Sync vs Async

Configuration Options

Option	Type	Default	Description
`mode`	`"sync" \| "async" \| "auto"`	`"auto"`	Backend variant; invalid values raise `ValueError`
`path`	`str`	`"praisonai_conversations.db"`	SQLite file path (sync store)
`table_prefix`	`str`	`"praison_"`	Table name prefix (alphanumeric only)

URL formats

db(database_url="sqlite:///conversations.db")          # relative path
db(database_url="sqlite:////absolute/path/to/db.db") # absolute path
db(database_url="sqlite:///:memory:")                # in-memory (temporary)

Best Practices

Use sync mode for multi-agent scripts

The sync_sqlite backend (mode="sync") uses per-call connection locking for multi-threaded agents.

Use absolute paths in production

Set the database path via environment variables and use absolute paths for deployments.

WAL is applied automatically

Every core SQLite store applies WAL through the hardened sqlite_connect factory, with a safe DELETE fallback on network and container filesystems — you no longer run PRAGMA journal_mode=WAL yourself.

Migrate to PostgreSQL at scale

SQLite handles thousands of conversations; move to PostgreSQL for multi-instance deployments.

PostgreSQL Persistence

Scale up when you outgrow SQLite

Database Persistence

Compare all persistence backends

Getting Started

Install

Core Concepts

Guides

Features

Models

Databases

Observability

Memory

Telemetry & Analytics

Knowledge

RAG

Persistence

Tools

Other Features

Developers

Configuration

Best Practices

Getting Started (No Code)

SQLite Persistence

Quick Start

How It Works

Sync vs Async

Configuration Options

URL formats

Best Practices

PostgreSQL Persistence

Database Persistence

​Quick Start

​How It Works

​Sync vs Async

​Configuration Options

​URL formats

​Best Practices

​Related

PostgreSQL Persistence

Database Persistence

Quick Start

How It Works

Sync vs Async

Configuration Options

URL formats

Best Practices

Related