Supabase says agents struggle to infer the current database schema from long migration histories, and reconstructing it by running migrations locally is too slow.

“That's really important for agents 'cause generally how you operate with Postgres is you have a migration file. Every time you make a change, you add a file to this migrations folder, and it's like a historical log.”

“Okay, so that's great. It's industry standard. But it- Imagine putting an agent across a thousand files and telling-- asking it, "Oh, what is the shape of this table?"”

“It has to guess through a thousand files, so- It has to recompile basically- It has to recompile... edit its weights. Yeah Or you have to launch the database, um, locally- Migrate, migrate, migrate, migrate...”

“run the migrations up, and then you inspect-- introspect the database. But that's too slow.”