Omniscio documentation
Browse all documentation
  1. Getting Started19
  2. Sessions & Agents134
  3. Inbox & Notifications67
  4. Projects & Tasks98
  5. Automation & Scheduling78
  6. Knowledge & Memory28
  7. AI Features71
  8. Integrations106
  9. Plugins & Marketplace36
  10. Cloud & Teams53
  11. Settings & Customization71
  12. Account & Billing28
  13. Troubleshooting79
  14. CLI & API Reference27
  15. Legal & Policies5
  16. Uncategorised17

Database Studio

Database Studio is a bundled plugin for looking inside your own Postgres and MySQL databases: browse tables, run SQL, sort, filter, page, export and copy the results, ask questions in plain English that a locked AI helper answers with tables and charts, and — only on a database where you turn on Allow changes — make changes that are tried first and applied only when you approve them.

Database Studio lets you look inside databases you already run — Postgres or MySQL — and, only where you allow it, change them. It opens from the projects rail. Its id is still database-checker.

What you can do

  • Browse — pick a table and see its columns and its rows, 50 at a time.
  • SQL — run your own query. Only a single SELECT or WITH statement is allowed, and it runs inside a read-only transaction that is always rolled back.
  • Work with the results — in Browse and on a SQL result: sort, filter, page, export and copy (below).
  • Ask — ask a question in plain English and get an answer in words, with the tables (and a bar or line chart where it suits) that back it up.
  • Changes — see changes waiting for your approval, approve or discard them, undo row changes, and turn Allow changes on or off for the selected database (below).

Working with results

  • Sort — click a column heading: ascending, then descending, then back to the database's own order. The database sorts the WHOLE table or query, not just the rows on screen.
  • Filter — Filter adds a condition on one column: is, is not, contains, starts with, is more than, is less than, is empty, is not empty. Add several and a row must match them all; remove one with its ×. The database does the filtering, over every row.
  • Pages — Previous and Next move through the rows: 50 at a time in Browse, and the database's row limit at a time on a SQL result. In Browse each row appears on exactly one page.
  • Export — save every row the current sort and filters match as CSV, JSON or Excel (.xlsx), whatever page you are on. An export holds at most the database's row limit (Most rows to return in that database's settings, 1,000 unless changed); when it stops there, the panel says so. Excel keeps numbers, dates and true/false as real values, and text as text.
  • Copy — click a cell, then Copy cell (or ⌘C / Ctrl+C) to copy its whole value, even when the cell shows it shortened. Copy table copies the rows on screen so they paste as a table into a spreadsheet or a document.

Making changes

Changes are off for every database until you turn on Allow changes on the Changes tab. You are asked to confirm first. Only you can turn it on, in the panel; nothing else can — not an AI, not another Claude session, not the command line.

With it on:

  • Your own changes — on the SQL tab, Preview change (⌘⇧↵ / Ctrl+Shift+Enter) tries an INSERT, UPDATE, DELETE, or a table change (CREATE / ALTER / DROP TABLE, CREATE / DROP INDEX) and shows exactly what it would do. In Browse, double-click a cell to edit it (Enter to check, Esc to cancel, Empty to clear it). Nothing changes until you click Apply.
  • Proposed changes — the AI helper (when you ask it for a change) and your other Claude sessions can only propose. Database Studio tries the change, keeps it waiting, and posts an inbox note such as "Database Studio wants to change 12 rows in orders". Open Database Studio and approve or discard it on the Changes tab.
  • Tried first — every change is run for real and then undone, so the preview shows how many rows it touches and the rows before and after (and, on Postgres, how the tables would change). When you approve, it is measured again: if the data moved in the meantime, nothing is applied and you see the new preview instead. A change of several statements applies all or nothing.
  • Not tried first — MySQL cannot try a table change without making it, and a MySQL table on an engine without transactions (MyISAM) would really be written. Those changes say so plainly, are approved without a trial, and cannot be undone.
  • Undo — a row change of up to 10,000 rows can be undone afterwards: Undo… prepares a new change that puts the old values back, which you check and approve like any other. Every preview says when a change cannot be undone, and why.
  • Editing a cell works in any table, even one with no key column: the change must touch exactly one row, or it is refused and you are asked to reload.

Turning Allow changes off stops every waiting change from being applied.

How Ask works

Ask is a conversation with an AI helper about ONE database.

  • It can only ask. The helper runs in a session the app locks to talking only: it has no tools, cannot run commands, cannot read your files, and every permission request it makes is refused. To see data it asks Database Studio for a look-up — list the tables, show a table's columns, sample some rows, or run one read-only query — and Database Studio runs it on that conversation's database through the same read-only checks as the SQL tab.
  • You see how it got there. Each look-up is a numbered step. While it works the steps appear live; after it answers they fold into "How I got this".
  • Saved answers are snapshots. Each conversation is kept with the date its data was read ("as of …"). "Re-run with today's data" asks every question again. Only the rows an answer actually showed are kept, and deleting the database from the list deletes its conversations.
  • Continue in chat opens the conversation as an ordinary chat in Omniscio. It stays locked.
  • Think harder uses a stronger model for a new conversation. It is slower and costs more.

What is sent to the AI

To answer, the helper's look-ups — table names, column names and the rows it reads (at most 50 per look-up) — are sent to the AI model. Before the first question on each database you are told this and asked to continue. The helper itself never changes anything: it can only propose a change for you to approve (see Making changes).

The Database Studio AI switch on the Ask tab turns the helper off for that database. It covers Database Studio's own helper only; your other Claude sessions can still read that database through the plugin's command-line endpoints.

If you are not looking at the panel when an answer arrives, an inbox note links back to it.

Database Studio shows short confirmations (such as "Table list reloaded") in Omniscio's own notification area. After updating, Omniscio asks you once to approve this, in Settings → Plugins.

Needs

Omniscio 0.1.111 or newer — the version whose sessions can be locked. On an older app Ask says to update and sends nothing.

Last verified 2026-10-13