AI & keys
Watching what a coding agent does
See an agent’s query results in AddisDB’s own table, add a project’s databases from its env file without the agent reading it, follow a run step by step, and get a rollback plan with every migration.
Once a coding agent is set up with AddisDB (see “Using AddisDB with a coding agent”), it does more than answer in text. This page covers what you see while it works, and the plan you get before it changes anything.
Query results in AddisDB’s table
When an agent runs a query, the rows come back in AddisDB’s own result table, not as a block of text. You see the connection and its environment, and you can filter, sort, expand a row, or open the result in AddisDB. A query panel lets you copy the SQL, edit it and run it again; the agent is then handed your run, not its own.
- In an agent app that can show interactive views, the table appears right in the chat.
- Where it cannot, AddisDB writes the same page to a file on your machine for you to open.
- An agent in a terminal prints the table as text.
Adding databases from an env file
If an agent finds that a project’s database is not in AddisDB yet, it can hand AddisDB the path of the project’s env file (a .env, or the file a hosting provider’s CLI pulls down). AddisDB reads the file itself. The agent never sees a password, a token or a connection string from it.
- AddisDB lists the databases it found and asks you to approve them, on a screen you can see.
- A pooled and a direct address for the same database become one connection.
- A database you already have is skipped, not added twice.
- A file named for production has its connections tagged prod.
The agent gets back only each connection’s name, engine, host and environment. Passwords go into your system’s credential store, the same as any connection you add yourself. A remote database added on the Free plan is saved with a note that opening it needs a paid plan.
Following a run live
When an agent starts a migration or a workflow, AddisDB opens a run monitor. It shows each step as it starts and ends and how long it took, every database the run touches with its environment, and a plain warning when the run can change prod. You can shrink it to one line or put it away; the run carries on, and the agent banner brings it back. Monitor opens the live view of a database the run is using, and Stop abandons the run and refuses the agent from then on.
If the agent is stopped or disconnects, the run is closed with the reason. It is never left spinning on screen.
A workflow that reaches prod is always asked for as a prod request. The approval names each database and its environment, and an earlier yes never covers it.
A rollback plan for every migration
AddisDB refuses a migration from an agent that does not come with a way back: either SQL that undoes the change, or a note explaining why nothing can undo it. Before you approve, the dialog shows the plan from start to finish, the statements that will run, and the rollback.
- The rollback is checked the same way as the migration, so its risks are in front of you too.
- It is saved as a .sql file before the change runs, and the run monitor shows where.
- Review in Migrations opens the rollback for you to read. It only runs if you run it.