Schema context, sent with every question.
Add a column this morning and it knows about it. Rename a table and the context follows. You control the scope: exclude individual objects, or turn schema context off entirely.
It writes the SQL. You decide what runs.
No pasting your schema into a chat window. pgen introspects the live catalog - tables, foreign keys, functions, custom types, extensions, server version - and sends it with your question, trimmed to fit whichever model you chose.
Add a column this morning and it knows about it. Rename a table and the context follows. You control the scope: exclude individual objects, or turn schema context off entirely.
There is no pgen server in the path. Your schema and your question go straight from your machine to the provider you picked - we never see either. Point it at Ollama and nothing leaves the machine at all.
Anthropic, OpenAI, Google, a local Ollama, or any OpenAI-compatible endpoint you host yourself. Keys are stored in the operating system keychain, not in a config file, and never sent anywhere except the provider they belong to.
The safety layer was built before the assistant was. It applies to SQL the model wrote the same way it applies to SQL you wrote, and none of it can be disabled from a prompt.
SELECT c.id, c.name, sum(o.total_cents) …UPDATE invoices SET sent_at = now() …DROP TABLE customersALTER TABLE orders ADD COLUMN …Today the assistant writes SQL and you decide what runs. Here's what's coming next - all of it arriving behind the same approvals you already control.
Bring up a table you've never mentioned and the assistant goes and finds it. You won't have to describe your own database to it before asking a question.
The assistant can safely try a query before it gives it to you, so what lands in your editor is something it has already confirmed returns what you asked for.
Point it at a query that's dragging and get a straight answer about what's holding it up - without having to read a query plan yourself.
Get a specific recommendation with the reasoning behind it, instead of guessing which column to index and hoping it helps.
Query plans, connections, searchable history, import and export - the parts you'd use every day even if the AI didn't exist.
Every node with its cost and time, the expensive branch marked red, and a plain sentence telling you which index would fix it - instead of a plan you have to decode yourself.
Tag connections as prod, staging, or local and filter by environment. ⌘P switches between them. Every query you've run stays searchable.
Column mapping with type inference and conflict resolution on insert. Move a Parquet dump through Postgres and out to CSV without reaching for a shell.
If it speaks the wire protocol, pgen connects. Cloud, container, or laptop - paste the URL and you're in.
Free, every feature, no account. Add your own API key when you want the assistant on, or run it against a local model and skip the key entirely. PRO arrives later for teams that need cloud sync and managed inference.
We use analytics to understand which pages get visited and how many people download pgen. See our privacy policy.