cel-memory-sqlite 0.2.1

SQLite-backed local memory for AI agents, implementing cel-memory with FTS and vector search.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

# cel-memory-sqlite

[![crates.io](https://img.shields.io/crates/v/cel-memory-sqlite.svg)](https://crates.io/crates/cel-memory-sqlite)
[![docs.rs](https://docs.rs/cel-memory-sqlite/badge.svg)](https://docs.rs/cel-memory-sqlite)
[![CI](https://github.com/dimpagk92/cel-memory-sqlite/actions/workflows/ci.yml/badge.svg)](https://github.com/dimpagk92/cel-memory-sqlite/actions/workflows/ci.yml)

SQLite-backed local memory for AI agents. Implements
[`cel-memory`](https://crates.io/crates/cel-memory)'s `MemoryProvider` trait with single-file storage,
FTS, and vector search through [`sqlite-vec`](https://github.com/asg017/sqlite-vec).

**Status:** v0.2.0 on [crates.io](https://crates.io/crates/cel-memory-sqlite) — implements the full `MemoryProvider` surface: writes, sessions, hybrid (vector + FTS + recency) retrieval fronted by a TTL+LRU cache, summarization and daily/rule-week rollups (via an injected summarizer), aging sweeps, export, stats, and bulk re-embed.

## Purpose

Use `cel-memory-sqlite` when you want a local, embeddable `MemoryProvider`
backend without running a separate database or vector service. It is designed
for agents, CLIs, desktop apps, local servers, and test harnesses that need
durable memory in one SQLite file.

## What's Included

- `SqliteMemoryProvider` — `MemoryProvider` impl backed by SQLite (one file, no separate process).
- `Embedder` / `MockEmbedder` — re-exported from [`cel-memory`](https://crates.io/crates/cel-memory) (since 0.2.0).
- `FastEmbedEmbedder` behind the `fastembed` feature — local ONNX runtime + `bge-small-en-v1.5` (~130 MB model download).
- Schema migrations for `memory_chunks`, `memory_vec` (sqlite-vec virtual table), `memory_fts` (FTS5), sessions, access log, eviction log.
- `sqlite-vec` extension loaded at connection open; the `memory_vec` virtual table is available without extra setup.

## Design

- **Single SQLite file.** One file to back up, encrypt, ship to compliance. No separate vector service, no second process to manage.
- **Brute-force vector scan up to ~1M chunks per user.** `sqlite-vec` is fast on Apple Silicon (5–30 ms at typical personal-memory scale). HNSW is a drop-in upgrade when `sqlite-vec` ships it.
- **Hybrid retrieval**: vector + FTS + recency, weighted per `RetrievalProfile`, fused with reciprocal-rank fusion and fronted by a short-TTL LRU cache.
- **Governance-first.** Every write consults the optional `MemoryWriteHook` from `cel-memory` — a rule engine can redact or veto.

## Example

```rust
use std::sync::Arc;
use cel_memory_sqlite::{MockEmbedder, SqliteMemoryProvider};

let provider = SqliteMemoryProvider::open(
    "memory.sqlite",
    Arc::new(MockEmbedder::new()),
).await?;
// Use as cel_memory::MemoryProvider — same trait as BasicMemoryProvider.
```

Run the complete example:

```sh
cargo run --example basic
```

## Features

- `fastembed` — enables `FastEmbedEmbedder` for local embeddings. Off by default to avoid the 130 MB model download in dev workflows.

## Upgrading from 0.1.x

Depends on **`cel-memory` 0.2.0**; import `Embedder` from `cel_memory` or keep
using the sqlite re-export. See the
**[0.2 migration guide](https://github.com/dimpagk92/cellar/blob/main/docs/migration-0.2.md)**.

## License

Apache-2.0