Supabase Explorer Brings Database and Log Queries Together.

Explorer is the new query editor in the Supabase Dashboard, and it changes where you go to debug a problem. Instead of switching between a SQL editor for your database and a separate logs viewer, Explorer queries both from the same screen.

The second piece is Notebooks. A Notebook is a file that lives in your project's supabase folder, holding saved queries alongside markdown notes explaining what they do and why. Once saved, a Notebook is not a one-off: anyone on the team can open it and rerun the same investigation, and because it is a plain file in the project, an AI agent can run it too.

Source: Read the official announcement.

Most production issues get investigated once, solved, and forgotten, which means the next person who hits the same symptom starts from zero. Saving the queries and the reasoning as a Notebook turns that one-off debugging session into something repeatable. A support ticket about a missing row becomes a Notebook with the query that finds it and the log pattern that explains why. Six months later, someone else runs it again instead of re-deriving it.

Other Supabase updates include DBArena for reproducible Postgres benchmarks and the Multigres private alpha for automatic failover. Together they point at a dashboard built for teams running real production databases, not just prototypes.

What is Supabase Explorer? Explorer is the new query editor in the Supabase Dashboard. It queries both your Postgres database and your project logs from one place, so you can trace an error back to the data that caused it without switching tools.

What are Notebooks in Supabase? A Notebook is a file saved in your project's supabase folder that holds a set of queries plus markdown notes describing what they investigate. Anyone on the team can open and rerun a Notebook, and because it is a regular file, an AI agent can run it too.