Database Browser

Where to find it

Connect a database and a Database tab appears in the workspace toolbar — it is one of the tabs an integration brings with it, so it shows up only for projects that have one. The same browser is also reachable inside the Backend tab under Database. It shows the schema of your project's PostgreSQL database — the same DB that gets created when you connect PostgreSQL via the Integrations menu.

What you can do

• Browse tables — pick a table from the sidebar, see all columns with their types and constraints, page through rows
• Search & filter rows by any column without writing SQL
• Inspect schema — primary keys, foreign keys, indexes, defaults
• Edit rows — add and change rows directly. A table needs a primary key for this; without one the browser is read-only
• Ask the agent for SQL — there is no query console in the browser. Ask in chat and the agent runs the statement; the executed SQL is shown in the chat
• Migrations — every schema change the agent applies appears here as a Flyway-style versioned migration; you can see the history

Dev vs Prod

The browser switches between your dev (workspace) database and your prod (published) database via a top-right toggle. Concurrent writes are isolated; running queries on prod doesn't touch dev and vice versa.

Safety

The browser has a read-only mode by default. Destructive statements (DROP, DELETE without WHERE, TRUNCATE) require explicit toggle to write-mode and a confirmation. Migrations are the canonical way to alter the schema — direct DDL is discouraged because it desyncs from the migration history.

Asking the agent about your data

The AI chat can also reach the database when you ask data questions ("how many orders last week?", "which user spent the most?"). The agent uses a read-only role with row limits and statement timeouts, so it can't accidentally wreck anything.