The Supper SQL IDE Keeps SQL in the Analytics Workflow
AI has made it easier to begin an analysis with a question. It has not changed the fact that many data teams already have SQL they trust, or that experienced analysts often want to inspect the query behind an answer.
The useful workflow moves in both directions. An analyst may use Supper to explore a question, open the resulting SQL to check the retrieval logic, then return to the conversation with an adjusted query. They may also begin with a query they already know and use the results to start a broader analysis.
Supper's SQL IDE gives technical users a place to do that work without leaving the product. It is a full SQL workspace connected to Supper's agentic analytics experience.
Bring the query you already have
Many analytical tasks do not start with an empty prompt. An analyst may have a trusted query from a previous report, a statement shared by a colleague, or a retrieval pattern they use every month.
That query can be the starting point in Supper. A user can write or paste SQL into the IDE, run it, and use the returned data as the basis for a conversation with Supper. The agent can help investigate the result, identify patterns, or take the analysis in a direction that was not obvious from the original query.
There is no reason to translate a precise query into a vague natural-language request just to begin using an AI tool. When the retrieval logic is already known, SQL is the clearest way to express it.
Inspect the SQL behind an answer
The workflow also runs the other way. When Supper retrieves data during a conversation, technical users can open the underlying SQL in the IDE and work with it directly.
This is useful when an analyst wants to check a join, adjust a filter, or understand how the agent reached a result. They can edit the query, run it again, and bring the updated data back into the conversation when they want help with the next stage of the analysis.
The agent does not have to be a black box. The SQL IDE gives users a direct route from the answer they received to the query that produced it.
A SQL workspace inside Supper
The Supper SQL IDE is built for the work technical users already do in dedicated query tools. It supports table and column search, autocomplete, saved queries, access to previous SQL versions, multiple tabs, SQL dialect selection, and configurable result-row caps.
Those capabilities matter because query work is rarely a single draft. An analyst may compare two versions of a statement, keep a useful query for later, or work across several tabs while checking a data model. The IDE keeps that work close to the conversation and the data it supports.
Supper's own data administrators helped shape the feature. They were often opening a separate SQL tool to inspect or adjust a query that Supper had generated. The IDE removes that extra handoff.
AI can help without taking over the query
The IDE includes lightweight AI assistance for users who want a starting point. Someone can describe the retrieval they need and receive an initial SQL scaffold based on the data model, then inspect and modify it before running the query.
That experience is intentionally narrower than Supper's main chat agent. The IDE assistant helps a technical user get to the first draft of a query. Supper chat is where someone can ask an open-ended question and let the agent take on more of the analytical process.
Both have a place in the product because they support different moments in the work.
SQL and agentic analysis belong in the same process
The SQL IDE is designed for people who already understand their organization's data and want direct control over retrieval logic. For them, SQL is not an alternative to agentic analysis. It is one way of steering it.
Business users can stay in the conversational experience when they want to ask a question without dealing with the technical details. Analysts can begin in the IDE when the query is known, or move there when they need to inspect the work. Both paths can lead into the same Supper analysis.
That connection is the point of the IDE. It keeps SQL, results, and agentic analysis in one place, so technical users do not have to move context between separate tools whenever the work shifts from a question to a query.
Frequently asked questions
What is Supper's SQL IDE?
Supper's SQL IDE is an integrated SQL workspace for technical users. It lets them write, inspect, edit, save, and run SQL while staying connected to Supper's conversational and agentic analytics workflows.
Can I inspect the SQL generated by Supper?
Yes. SQL generated during Supper's data-retrieval workflows can be opened in the SQL IDE, where a user can inspect, edit, and run the query.
Can I start a Supper analysis with existing SQL?
Yes. A user can begin in the SQL IDE with a query they already have, then use the query and its returned data as the basis for a Supper conversation.
Does the SQL IDE include AI assistance?
Yes. The IDE includes a lightweight assistant that can create an initial SQL scaffold. It is designed as a starting point for technical users who want to inspect and refine the query themselves.