Builder console
Look inside your live app and fix it, from a console or your agent.
Once an app is live you need to correct a row, answer a question the screens don't, see why a job failed, rotate a key or undo a mistake. The builder's Backend panel does all of it on the development or production database, and every production change is backed up first.
select title, capacity, booked
from session where booked = capacity;| title | capacity | booked |
|---|---|---|
| Breath Reset | 12 | 12 |
| Core Pilates | 10 | 10 |
Read-only, rolled back · prod is backed up before every change
- Dev / Prod switch
- Prod asks before every change
- SQL and rows
- A table editor and a SQL pane
- Live events and logs
- Change events, requests, errors
- Same tools via MCP
- Your agent operates it too
How you operate an app
Open the project's Backend panel. The Dev / Prod switch picks the database; on Prod the panel turns amber and every change asks for confirmation.
Browse and edit rows, run SQL, read the full schema, follow live events, run a workflow now, replay failed jobs and manage secrets.
Or ask your agent in plain words. The same operations are MCP tools, CLI commands and HTTP routes, each taking env dev or prod.
> on prod, set the capacity of Tuesday's Sunrise Flow to 20
edit_rows { "table": "session", "env": "prod", "op": "update",
"id": "852eddbb-…", "patch": { "capacity": 20 } }
→ { "succeeded": 1, "snapshotId": "prod-…-agent-editrows" }
tail { "kind": "events", "env": "prod", "since": "3h" }
→ { "table": "session", "op": "update", "capacity": 20 }
Every pane you need after launch
Data
Browse any table and edit or add rows; writes go through the app's rules, as they would from a screen.
SQL
Several statements in one transaction, reads and writes. A read-only script runs rolled back.
Schema
Tables, keys, indexes, views, functions, triggers and policies, each marked contract, platform or hand-made.
Workflows
Run now with a JSON input on dev or prod, and Failed jobs with Replay.
Logs and Live
Workflow runs and their log lines, payments and files; change events, topic messages, requests and errors as they happen.
Secrets
Environment variables and secrets for dev, prod or both. Values are never shown again once saved.
Edit a row on prod, then roll it back
This is the real builder, recorded: a snapshot, a row edit on production, a restore, SQL on dev, Run now on a workflow, live events and secrets. The operating guide shows the same edit made by an agent.
Works with
Builder console: common questions
Can I run SQL on production?
Yes, from the SQL pane with the Prod switch on, or the sql tool with env prod. Production is backed up before each change and every change asks for confirmation.
Should I edit data with SQL or edit_rows?
Prefer edit_rows for data: it goes through the app's access, rules and workflows. SQL writes go past them, which is useful for fixes but bypasses business logic.
Can my coding agent operate the app?
Yes. The same operations are MCP tools (sql, edit_rows, describe_schema, snapshots, deploys, run, tail, secrets), limited by the scopes you granted.
Are production changes audited?
Yes. Every write records who made it, which tool and which environment, never a secret value.