Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.querybear.com/llms.txt

Use this file to discover all available pages before exploring further.

Turso is an edge database built on libSQL, an open-source fork of SQLite. It’s SQLite-compatible, so QueryBear can query it through the same read-only security gateway used for local SQLite.

​
Connection options

Turso databases can be reached two ways:
  1. Remote (libSQL URL + auth token) — the database lives on Turso’s edge. You connect with a libsql:// URL and an auth token.
  2. Embedded replica / local file — if you sync a Turso database to a local SQLite file, point QueryBear at that file like any local SQLite database.

​
Get your Turso connection details

  1. Install the Turso CLI and run turso db show <database> to get the database URL (libsql://<db>-<org>.turso.io).
  2. Create an auth token: turso db tokens create <database>.

​
Add the connection to QueryBear

In the QueryBear dashboard → Connections → New connection → SQLite / libSQL:
  • For remote Turso: provide the libsql:// URL and auth token.
  • For an embedded replica: provide the absolute path to the synced local file.

​
Turso-specific notes

  • Read-only is enforced at the QueryBear gateway regardless of the token’s scope. For defense in depth, generate a read-only auth token in Turso.
  • ATTACH DATABASE is blocked at the parser, as with all SQLite connections.
  • Edge latency: Remote queries hit the nearest Turso replica. QueryBear’s query timeout accommodates network round-trips.

​
Connect to your AI client

The client setup is identical to local SQLite: