LanesLanes
Docs/Desktop/Power Features/Databases Explorer

Databases Explorer

Browse SQLite databases and run read-only SQL queries without leaving Lanes.

Lanes includes a built-in Databases Explorer so you can inspect SQLite databases in your project -- browse tables, peek at rows, and run read-only SQL queries -- without leaving the app or reaching for a separate database tool. It lives in the context sidepanel, right alongside the File Browser.

Opening the Databases Explorer

Open the Databases Explorer from the context sidepanel toolbar at the top of an issue -- click the Databases icon (the database symbol) next to Context, Changes, and Working Folder. You can also reach it from a project's menu in the sidebar. It opens as a full-width panel.

The explorer works against the working folder linked to the current issue. If no folder is linked yet, you'll see "No working folder linked" -- add or attach a project folder first (see the File Browser docs).

Finding Your Databases

When you open the explorer, Lanes automatically scans the working folder for SQLite database files so you don't have to hunt for them.

  • It looks for common SQLite extensions: .db, .sqlite, .sqlite3, and .db3.
  • It searches subfolders too, while skipping heavy directories like node_modules, .git, target, dist, build, .next, and .venv.
  • Throwaway SQLite sidecar files (-wal, -shm, -journal) are ignored.

The Database picker shows how many databases were found -- for example Database (5) -- and the path of the one you're viewing. While the scan runs it shows "Scanning…", and if nothing turns up it shows "No database found". Click Rescan databases any time to pick up files added after you opened the panel (for instance, a database an agent just created).

Browsing Tables and Views

Once a database is selected, its tables and views are listed on the left under Tables, with a count next to the heading. Tables and views have distinct icons, and internal sqlite_* system tables are hidden to keep the list focused on your data. Use the refresh button to reload the list after the schema changes.

Click any table or view to preview it -- Lanes runs SELECT * FROM "<name>" LIMIT 100 for you and drops the first rows straight into the results grid, so a single click is enough to see what's inside.

If a file can't be read, the explorer tells you why (for example, "Unable to open database: it is encrypted or not a valid SQLite database").

Running SQL Queries

Above the results is a full SQL editor powered by Monaco -- the same editor engine used in the File Browser -- with syntax highlighting, line numbers, and theme matching. Type any read-only statement (SELECT, PRAGMA, EXPLAIN, and so on) and run it with:

  • ⌘↵ (Ctrl+↵ on Windows/Linux), or
  • the green Run button.

Drag the handle below the editor to give yourself more room for a longer query.

Reading Results

Results appear in a grid beneath the editor with sticky column headers that stay in place as you scroll. A status line summarizes each run -- the number of rows returned, or the SQL error if something went wrong. Cells render naturally: NULL values show in muted italics and booleans as true/false. Hover a long, truncated cell to see its full contents in a popover.

To stay responsive, results are capped (500 rows by default). When a query returns more, Lanes appends a note that the result was truncated, so you always know you're seeing a partial set. Statements that return nothing show "Statement executed. No rows returned."

Read-Only by Design

The Databases Explorer opens every database in read-only mode. You can browse and query freely, but writes -- INSERT, UPDATE, DELETE, ALTER TABLE, and the like -- are rejected. That makes it safe to poke around a live database (including one an agent is actively using) without any risk of changing or corrupting your data.

Switching Databases and Projects

If your project has more than one database, click the Database picker to switch between them; the active one is marked with a checkmark. When you work across multiple project folders, the Current Repository picker lets you jump to another folder's databases without leaving the panel.

Tips

  • Pair the explorer with an agent session to verify what the agent actually wrote -- run a quick SELECT to confirm a seed script populated the tables or a migration landed as expected.
  • Use PRAGMA table_info("<table>") to inspect a table's columns and types.
  • Because it's read-only, it's a safe way to explore an unfamiliar database: list the tables, preview a few rows, and build a mental model before touching anything.
  • It shares the pane with the rest of the review tools. Read the migration in the editor, check the diff in Changes, then confirm the result here, without opening a separate database client.