SQL Sage for DBeaver turns questions into safe, schema-aware SQL on your live connection. Signed in with your own Claude or ChatGPT/Codex account — no API key, no extra AI bill. Read-only by default, every statement classified and logged.
DBeaver’s built-in AI is good, and it does support Claude — in PRO, with your own API key and credits. Here is the honest split.
| SQL Sage | Built-in AI — Community | Built-in AI — PRO | |
|---|---|---|---|
| Anthropic Claude as the model | ✓ Yes — signed in with your own Claude | No — Claude is a PRO-only provider | Yes — Claude is a PRO-only provider |
| What the AI costs you | ✓ Nothing extra — the Claude or ChatGPT plan you already have | Your own provider account — an API key billed per token, a GitHub Copilot plan, or (since 26.2) a ChatGPT subscription | |
| Chat in plain English | ✓ Yes | Yes | Yes |
| Explain query · fix SQL errors · describe objects | ✓ Yes | No — PRO-only features | Yes |
| Tool-use over your live schema (MCP) | ✓ Yes | No — PRO-only feature | Yes |
| Runs the SQL for you | ✓ Yes — every statement classified first | Yes — chat offers Execute, and the @ai command runs the query it writes | |
| Write / DDL gate | ✓ Parser chokepoint, fail-closed on anything unproven, confirmation dialog with the full SQL — and no setting turns it off | Confirmation for modification and schema changes is on by default, but it is a preference you can switch off | |
| Per-connection read-only + global kill-switch | ✓ Set a connection to Read-only or No execution for SQL Sage’s assistant and its outward MCP bridge; a global kill-switch freezes all AI-initiated query execution, reads included | Not documented | |
| Local audit trail | ✓ Hash-chained JSONL of every classification decision | Optional logging of AI requests to the debug log | |
| Works in DBeaver Community | ✓ Fully — everything above | Chat and the @ai command only | |
Every claim in the DBeaver columns is checkable in their own documentation — DBeaver AI Assistant docs: PRO-only providers carry an “available only in PRO” marker, and PRO-only features a note reading “available in Lite, Enterprise, and Ultimate editions only”. Read 19 August 2026; the Claude and cost rows rechecked 19 November 2026 against the DBeaver Community release notes (26.2, 30 August 2026: subscription sign-in for OpenAI) and the OpenAI integration page (API token or ChatGPT account). SQL Sage is not affiliated with DBeaver Corp.
Built for people who are careful about what an AI touches on a production database.
Only your SQL and schema metadata (table / column names and types) are sent to the model — never row data. Sending result values is off by default and takes two steps: allow it in Preferences, then type /share on in the chat. /share on covers that conversation only.
Every statement is classified before anything reaches the database, one statement per call, and only a proven read runs automatically — on SQL Sage’s own connection, never inside your editor’s transaction. INSERT / UPDATE / DELETE / DDL is never executed without a confirmation dialog showing the exact SQL. Mark a connection read-only and the AI cannot write to it at all; a global kill-switch freezes every AI-initiated statement instantly.
Authentication uses your local claude / codex login. SQL Sage never sees, stores or transmits an API key or token.
Every tool call and executed statement is written to a local, hash-chained JSONL log — tamper-evident and provable for your security team, and nothing leaves your machine.
Describe what you want; SQL Sage writes SQL for your dialect, grounded in the live schema — tables, columns, keys, indexes.
Always shows which connection and engine an answer is for. Switch connections and the chat follows.
The model inspects metadata and runs read-only queries via tools: get_schema, describe_object, explain_query, find_related, run_query.
Grabs the real error from your last failed run and explains the cause — then proposes a corrected query.
Right-click → SQL Sage: Explain, Optimize, Fix, Format, Generate. Copy or insert generated SQL into your editor.
Answers stream with visible tool-run status and one-click cancel. A READ / WRITE / DDL badge on every SQL block.
Go deeper: how keyless sign-in works with your own Claude or ChatGPT/Codex account, and one copilot across five database engines.
Start free — no signup. Or take a 30-day Pro trial, no card required.
First 30 days: full Pro. No card. When the trial ends it stays free forever — you keep everything above.
Install freeLifetime = the current major version plus one year of updates. Prices in USD, billed via Paddle. Free for students and open-source maintainers on request.
Requirements: Windows, DBeaver 26.x, and the claude or codex CLI installed and signed in (the panel shows your sign-in status and helps you log in). Linux and macOS are not supported — see the documentation.
https://sqlsagedbeaver.lumasoft.org/updatesite
Added the old address https://sqlsagedbeaver.lumasoft.pl/updatesite earlier? It keeps working — same update site, nothing to change.
Ctrl+Alt+A).SQL Sage uses your local CLI login. In a terminal sign in to the Claude or Codex CLI (run claude and use /login, or codex login), then click check again in the panel. No API key is ever entered into SQL Sage.
Yes. SQL Sage is a third-party AI assistant for DBeaver that you sign into with your own Claude (Anthropic) or Codex (OpenAI / ChatGPT) CLI — no API key, no separate AI bill. Switch providers in the chat panel; the model reads your live schema and writes SQL for your dialect.
Yes — SQL Sage installs into DBeaver 26.x (Community and PRO) from a p2 update site, adding AI chat, query and error explanation, and schema-aware SQL generation on your live connection.
Install and every Pro feature is unlocked for 30 days — no signup, no card, nothing to cancel. When the trial ends the plugin quietly drops to the Free tier; buy a Pro key any time to unlock again. Your work and settings stay put.
SQL Sage sends only your SQL and schema metadata — not row data — so token use per question is small. Usage counts against your existing Claude/Codex plan under its terms; SQL Sage adds no separate AI fee.
Only your SQL and schema metadata (table/column names and types) are sent to the model — never your row data. Sending result values is off by default. It needs two deliberate steps: allow it in Preferences → SQL Sage, then type /share on in the chat. The Preferences setting alone sends nothing, and /share on lasts only for that conversation — it resets on New Chat, when the chat view closes and on restart. A local audit log records what ran.
Relational engines DBeaver connects to — PostgreSQL, MySQL/MariaDB, Oracle, SQL Server and SQLite. Dialect and capabilities are detected from the connection.
Queries are classified before execution: only a proven read runs automatically, on SQL Sage’s own connection rather than in your editor’s transaction, and writes or DDL are never executed without an explicit confirmation dialog showing the exact SQL. Everything is logged locally. What we do not claim: an engine-enforced read-only transaction exists only on PostgreSQL and MySQL/MariaDB, and the query timeout depends on the driver — so on production, mark the connection Read-only or No execution. The safety model, limits included →
Yes. SQL Sage for DBeaver was previously named SqlSage for DBeaver; version 0.1.0 and earlier show the name SqlSage in Preferences and the install dialog.
Use your own Claude or Codex account under its provider’s terms of service. SQL Sage is a product of LumaSoft (LUMA sp. z o.o.). Not affiliated with Microsoft, Anthropic, OpenAI or DBeaver.