libsql
LibSQL / Turso
Edge SQL via libsql://, file:, or Turso HTTPS URLs.
libsql://my-db-org.turso.io?authToken=YOUR_TOKENThe story
Edge app team TursoFast ships SQLite at the edge with Turso replicas and keeps file:./data/local.db for offline dev on the train. Two connection shapes, one product — libsql:// for remote, file: for embedded.
Lead dev Casey pointed file:./data/app.db at the repo, opened the grid, edited rows offline, then switched to libsql://my-db-org.turso.io?authToken=... for staging sync. Auth token landed in the vault, not in git. sqlite: URLs normalize to file: internally so old snippets still work.
LibSQL is Postgres-grade studio UX on SQLite bones — local-first when you want it, edge when you need it.
Connection URL
Scheme: libsql://
Parameters
libsql://my-db-org.turso.io?authToken=YOUR_TOKEN
file:./data/local.db — Use file: or libsql:// for embedded SQL. sqlite: is normalized to file:.
Step 1
Local SQLite files
Casey clones the repo, connects with file:./data/app.db, and runs migrations from Query lab before coffee. No docker compose up for a simple schema check.
Schema and grid work fully offline — plane mode friendly.
file: and libsql:// paths for embedded SQL. sqlite: scheme normalized to file:. No server process required for file-backed databases. Relative paths resolve from Bridge working context.
Step 2
Turso remote
Staging deploy uses libsql:// with authToken query param. Casey saves Turso Staging, verifies row counts match local, and ships. Token never appears in Copilot context — only the saved name.
Same grid and catalog as Postgres tabs; only the wire layer changes.
Remote LibSQL/Turso via libsql://host?authToken=TOKEN. HTTPS replication semantics handled by the client. Encrypted vault storage for tokens.
Next
Explore the full feature guide: LibSQL guide