Introducing the Explorer!#
The Explorer is a unified workspace for interacting with your database and logs via SQL, chat and a new feature we are calling Notebooks. Explorer is an evolution of the SQL Editor and will replace it when the flag is enabled.
Notebooks aim to replace Snippets and Custom Reports. They can contain one or many SQL queries with surrounding markdown context. You can query both your own database and project logs which means they can be used for observability, growth tracking, recurring tasks etc. They can be managed and run in Studio as well as by the Supabase Assistant with user confirmation and later your own agent via code or MCP. Snippets are not visible in Explorer, we are instead looking at a migration path from Snippets -> Notebooks if needed.
Explorer is a glimpse at a future where reports and insights are generated on demand, personalized to your needs, with Notebooks being the first primitive.
Feedback#
- How was the transition from SQL Editor to Explorer? What can we do to help ease that transition?
- What do you use Snippets for and how would they translate to Notebooks? What other use cases are you using / plan to use Notebooks for?
- How has Notebooks or interacting with the Assistant changed your approach to observability/debugging? Does chatting with your logs feel natural? What can we improve?
- Any bugs or issues that you run into while using the Explorer or Notebooks
- Any other feedback, good or bad - we're reading everything in this thread! 🙂🙏
You may now give this a go by toggling this through the dashboard's feature preview section which you can access via the user dropdown in the header 🙂 🙏
[!NOTE] This feature preview is being gradually rolled out to users. Don't see it yet? Sit tight, and let us know you're waiting!