Your Postgres tables, next to the pages that show them.
midcode is adding a table editor and a SQL editor for the Postgres database behind your site. It finds the database from the connection string your project already has in its .env files (DATABASE_URL and the like), lists the tables with their columns and rows, and runs the SQL you write. A database that isn’t on your Mac opens read-only until you allow changes.
v1.1.2This is being built and isn’t in the version you download today. Leave your email to hear when it ships.
- Status
- In development
- Finds it from
- Your .env files
- Remote databases
- Read-only by default
- Credentials
- Stay on your Mac
01/What you can do
What’s coming for Postgres.
Tables without a second app
Every table in the database, with its columns and its rows, in the same window as the site.
A SQL editor
Write a query, run it, read the result as a table. Queries you save are kept with the project.
See the plan first
Ask how the database would run a statement, without running it.
Warnings that matter
An UPDATE or DELETE with no WHERE tells you it touches every row, and asks before it runs.
Found, not configured
DATABASE_URL, DIRECT_URL, POSTGRES_URL or Laravel’s DB_* values: midcode reads what the project uses. You can add a connection by hand too.
Read-only where it counts
A database that isn’t on this Mac may be the one your site runs on. midcode opens it read-only and says so.
02/How it works
Three steps. No new workflow.
Step 1: Open your project
midcode looks for the database the project already points at. Connection strings stay in the app’s main process and are never shown.
Step 2: Browse and query
Open a table to read its rows, or write SQL and run it. Save the queries you’ll want again.
Step 3: Allow changes when you mean to
A database on your Mac can be changed. One that isn’t opens read-only until you turn on “Allow changes”.
03/Good to know
The honest part.
What it doesn’t do
- Changes to a database have no undo and aren’t part of Publish: they happen in the database, for real.
- Migrations stay in your project’s own tools.
Coming next
- MySQL and Turso.
- Sign-in for your site, set up visually.
04/FAQ
Postgres questions. Short answers.
They’re Postgres, reached with a connection string, so they open like any other Postgres database. Being remote, they open read-only until you allow changes.
Nowhere. midcode reads the connection string from your .env on your Mac and connects from your Mac. A connection you add by hand is kept encrypted, outside the project.
It’s being built now. The email list at the bottom of this page is told first.
05/Goes with
The rest of your stack.
- In developmentSQLite. The .db file in your project, as tables you can read and query.
- Next.js. App Router projects, edited in their .tsx files. Metadata and pages too.
- Next releaseLaravel. Blade views, edited on the canvas. With or without Vite.
- Claude Code. A chat beside the canvas, with the element you point at as context.
Be the first to use it with Postgres.
midcode already edits your site on a live canvas. Download it now, and the data editors arrive as an update: every update is included.