From the first query to the deployment script, with the shortcuts you'd expect: Ctrl+Enter, F8, F5, F12, Ctrl+Space.
An editor that knows your schema
Completion with the real columns after alias., package members with their signatures, %ROWTYPE and cursor records. Go to definition — also into the database — references, rename, live diagnostics, multi-cursor and code folding.
SQL windows that keep up
Run the statement under the cursor, the selection or the whole script. A virtualized grid sorts, filters, charts and exports to CSV, Excel, JSON or INSERTs, and follows foreign keys to parent and child rows.
Edit data without locking it
Change query results in place, with no FOR UPDATE: changes are checked against the values you fetched, so someone else's update is reported instead of overwritten. Show SQL previews the DML.
PL/SQL from spec to body
Program windows with spec and body, compile errors you can click, an outline and a formatter your team can share. Test… writes a ready-to-run block for any procedure or function — records, collections and ref cursors included.
A debugger that sets itself up
Conditional breakpoints, step into, watches, Run to Cursor, and values you change while stopped. Hover a selection like l_order.lines(i) to see that element. At every stop it checks the plans of the SQL the code just ran, marks a misestimate on its line and lets the plan button blink; a click shows the real plan beside the code, estimated and actual rows side by side. When the database can't connect back, Debugger Setup finds out why — grants, ACL, host name, firewall — and fixes it. A profiler too.
See what the database is doing
A dashboard that says it plainly — “session 175 blocks 2 sessions, likely an uncommitted transaction” — the blocking tree, sessions and SQL with their plans and binds, ASH, AWR and SQL Monitor reports, tkprof for traces.
AI with the model you choose
Anthropic, any OpenAI-compatible API, a local model (Ollama, llama.cpp, LM Studio) or a command line tool. Generate SQL from your real tables, fix errors, explain plans. Each answer shows what was sent.
Compare, import, maintain
Schema compare with ordered sync scripts, data compare by key, CSV and Excel import with type inference, table export, and a maintenance scan for stale statistics, unusable indexes and dead rows.
Your code under version control
Open a folder as a project with its git status, compare a file with its object in the database, export a schema as one file per object, and deploy what changed in dependency order.