Crate recall_server 

Recall’s server half: SQLite persistence, LLM-assisted merge, and the HTTP API.

The routes, status codes, JSON shapes and auth behavior are deliberately identical to the Node implementation this replaces, because during a migration a machine still on the old client and one already on this binary talk to the same deployment.

Re-exports

pub use config::Config;

pub use config::ConfigError;

pub use config::TlsMode;

pub use server::Server;

pub use store::Store;

Modules

admin

recall-server admin: listing, renaming, removing and restoring the memory stored under a project key, from a shell on the server’s host.

audit

The audit log: a Merkle tree over every authenticated action, following docs/design/part5-plan.md’s “PR 1: audit” and “The audit chain”.

bootstrap

The one-time code that, beside RECALL_TOKEN, registers the first passkey for /admin.

config

Server settings.

merge

The semantic merge, which now lives in recall-worker.

server

The HTTP surface.

store

SQLite persistence.

Structs

Merger

Runs merges through a claude binary.

Functions

now

A timestamp in the format every stored row and every API response uses: JavaScript’s Date.toISOString() — millisecond precision, Z suffix, e.g. 2026-09-03T21:49:55.191Z.