Skip to main content
The sqlite backend persists sessions to a local SQLite file. It needs no external database service, but unlike local, sessions are written to disk and therefore survive across processes and restarts.

When to use

  • Single-node deployments that need persistence;
  • Local development where you want to keep past sessions;
  • Small data volumes with no need for distributed access.

Usage

If the DB file doesn’t exist, VeADK creates it automatically (including any parent directories) and resolves the path to an absolute one. You can also pass a connection string directly via db_url, in which case backend and local_database_path are both ignored:

Parameters

ShortTermMemory constructor parameters (sqlite)

Environment variables

The sqlite backend reads no environment variables; all configuration comes from constructor parameters. Need distributed persistence? Use MySQL or PostgreSQL.
Last modified on September 19, 2026