Skip to content

UI Tour

Where to click, what happens, and what the numbers on screen mean — one workspace area at a time.

This page is a road map: every item covers "where to click" → "what to do" → "why it matters". Deep dives (Editor, Result Grid, AI...) live in their own doc sections.

1. Left sidebar — data navigation

The sidebar is where every session starts: pick a connection, browse the schema, and open tables.
App logo / name (top-left corner)

What to do: Click to return to the Dashboard

Why it matters: A quick escape hatch back to the home screen from anywhere in the workspace.

Connections list

What to do: Click a connection to activate it; click the arrow to expand/collapse the database tree

Why it matters: The active connection is highlighted. The tree lists database → schema → tables/views/functions; double-click a table to open a DataGrid tab.

+ button (add connection)

What to do: Opens the new-connection dialog

Why it matters: Pick an engine with the visual picker, fill host/port/user/pass or paste a URI. The Test button verifies the connection before saving.

Search box (Ctrl+P)

What to do: Opens global search

Why it matters: Finds tables, views, and saved connections by name through the synced search index — type a few characters to jump straight to the object.

User avatar (top-right corner)

What to do: Opens the profile menu

Why it matters: Where you switch language, configure AI (Profile > Configure AI), view billing, sign out, and edit your avatar.

2. Editor & toolbar — writing and running SQL

The toolbar above the editor holds every execution action; these are the buttons you will use most.
Run button (▶) or Ctrl+Enter

What to do: Executes the selected SQL (or everything if nothing is selected)

Why it matters: Only the highlighted portion runs — useful in multi-statement files. Risky queries (DROP, DELETE without WHERE) show a confirmation dialog first.

Stop button (■)

What to do: Cancels the running query

Why it matters: The cancel happens on the server (pg_cancel_backend / KILL QUERY), not just by discarding the client-side result.

Format button (Shift+Alt+F)

What to do: Auto-formats the SQL

Why it matters: Reflows whitespace and line breaks for readability. Does not change query logic.

AI button (✨)

What to do: Opens the AI Assistant panel

Why it matters: The AI knows the active connection's schema — ask in plain language and it generates SQL, explains, or fixes queries for you.

Tab bar above the editor

What to do: Click to switch tabs, click X to close, middle-click to close quickly

Why it matters: Each tab keeps its own editor content, results, and scroll position. DataGrid and Query tabs can be open side by side for the same connection.

3. Result Grid & footer — reading results

The result-grid footer holds the most important numbers for judging your query.
The "100 / 1,247 rows" figure in the footer

What to do: Rows currently shown / total rows matching the query

Why it matters: The total is briefly cached in Redis so paging does not re-run COUNT(*). While pending it shows "…"

The "23ms" figure

What to do: How long the query took on the server

Why it matters: Measured from when the server receives the SQL until results return. Queries over 1s deserve an EXPLAIN (the Explain button or AI Explain).

The "windowed" / "cached" badge

What to do: Tells you where the data came from

Why it matters: "windowed" = the server returned only the visible page; "cached" = the result came from the short-term cache, near-instant.

Previous / Next / page-jump controls

What to do: Moves through data pages

Why it matters: The server applies the matching LIMIT/OFFSET — you never have to write pagination into your SQL.

Export button (CSV/JSON)

What to do: Exports the displayed result to a file

Why it matters: CSV preserves Excel-safe encoding and delimiters; JSON keeps nested structure. Only the visible page is exported — page through first if you need more.

4. Dashboard — what the numbers mean

The dashboard greets you every launch; its number cards are not just decoration.
The "Active Connections" number

What to do: How many connections you have saved

Why it matters: Counts your own connections plus those of organizations you belong to.

The "Queries Run" number

What to do: Queries executed in the current working session

Why it matters: Counts from this session's query history — reloading resets it to 0. See the full history via the Query History dialog.

The "Tables Accessed" number

What to do: How many sidebar tree nodes you expanded

Why it matters: An estimate of how much schema you explored this session — every table/view you opened to view is counted.

The "Recent Dashboards" list

What to do: Click a dashboard to open it in a tab

Why it matters: Each row shows the name, widget count, visibility (private/team), and last-updated date. The Share button invites teammates.

The "Team Activity" feed

What to do: Tracks who did what in the organization

Why it matters: Shows recent events: shared queries, dashboard edits, new comments. The small badge counts unread events.

5. Other areas — quick reference

AI Panel (Ctrl+J)

Chat with the AI about your data. Pick model/routing mode at the top, type prompts at the bottom, attach images/PDFs with the paperclip.

Dashboard tab (charts)

Open from Recent Dashboards or create new. Add chart widgets from query results; drag to arrange; Share to invite the team.

Query History dialog

Every query you ran with duration and status. Click an entry to re-insert it into the editor; filter by connection.

TeamPage

Manage the organization: members, roles, teamspaces, resource share policies, and backup/restore.

Active Queries panel

Lists queries currently running on the connection with durationMs; the cancel button on each row stops it immediately.

Connection health badge

The colored dot next to a connection name: green = healthy, red = error (hover for the message), gray = not yet checked.

Where to start?

If you are new: open the sidebar → create a connection (+ button) → test it → double-click a table to open the DataGrid → switch to a Query tab (Ctrl+N) and write your first SQL → Ctrl+Enter to run. That is the core Data Explorer loop.

Ready to explore data?

Join the community on GitHub to contribute to the smartest local database IDE.

Launch App