Supper SQL IDE: SQL and AI in One Analytics Workflow

There's a common assumption about AI and analytics: eventually, chat will replace SQL.

We don't think that's how sophisticated data teams actually work.

Sometimes you want to ask a question in natural language and let an agent determine how to retrieve and analyze the data. Other times, you already know exactly what query you want to run. And sometimes you want the AI to get you most of the way there, then open the SQL, inspect it, and make the last changes yourself.

That's why we built the Supper SQL IDE: a professional SQL workspace directly inside Supper, designed to let technical users move between SQL and agentic analytics without leaving the application.

Start with a conversation. Start with SQL. Move back and forth as the work demands.

What is Supper's SQL IDE?

Supper's SQL IDE is an integrated workspace for users who want direct access to SQL alongside Supper's agentic chat experience.

Technical users can write and refine queries, search tables and columns, use autocomplete, save queries, access previous versions of SQL, and work across multiple tabs. They can also control technical settings such as SQL dialect and maximum result rows.

But the most important part is where the IDE lives: inside Supper.

SQL doesn't become a separate workflow. It becomes another interface into the same analytical process.

A query created during a Supper conversation can move into the IDE for inspection and editing. A query written in the IDE can become the starting point for a new conversation or feed back into an existing one.

In other words:

Chat → SQL → IDE → results → chat

And just as importantly:

SQL → results → chat → deeper analysis

There's no required starting point.

Why build a SQL IDE when AI can already generate SQL?

Because technical users still want control.

In fact, one of the signals that led us to build the IDE came from our own data administrators. They were opening tools like DataGrip to inspect or adjust SQL produced by Supper.

The agentic workflow was useful, but when an experienced SQL user wanted to get closer to the query itself, they had to leave the product.

Customers also brought us another use case: sometimes the SQL already exists.

An analyst might have a trusted query from another tool. A colleague might send them a SQL statement. They might be continuing an analysis they've performed many times before.

In those cases, forcing someone to translate a precise SQL query back into a natural-language prompt creates an unnecessary cold start.

With Supper's SQL IDE, SQL itself can be the prompt.

Enter the query, retrieve the data, and use that result as the launchpad for a much richer conversation with Supper.

Start with SQL when you know what you want

Natural language is powerful when the question is open-ended.

SQL is powerful when the retrieval logic is already known.

Supper supports both.

Imagine you already have a query that retrieves exactly the customer segment you want to analyze. Instead of asking an AI system to recreate that logic from scratch, you can begin in the IDE with the SQL you already trust.

From there, the returned data can kick off an agentic workflow.

You might begin with a precise retrieval request in SQL and then move into broader questions about what the results mean, what patterns are present, or what analysis should happen next.

That makes SQL more than an implementation detail.

It becomes a launchpad for agentic analysis.

Inspect and edit AI-generated SQL

The workflow also runs in the other direction.

When Supper retrieves data during a conversation, technical users can access the underlying SQL and move it into the IDE.

That matters because sophisticated users often don't want a black box.

They may want to:

• Inspect how a query was constructed.
• Adjust a filter or join.
• Refine the retrieval logic.
• Use the generated query as the beginning of a more technical workflow.
• Return the updated SQL to the conversation and keep analyzing.

The goal isn't to make every Supper user become a SQL expert.

It's to give SQL experts the level of control they already expect.

A professional SQL workspace inside Supper

We built the IDE around the workflows analysts already use in dedicated SQL tools, incorporating feedback from customers and the practices of our own technical teams.

The Supper SQL IDE includes capabilities such as:

• Table and column search to navigate the data model.
• Autocomplete to make query authoring faster.
• Saved queries for SQL you want to return to.
• Versions of previous SQL statements so you can revisit earlier work.
• Multiple tabs for working across several queries at once.
• SQL dialect selection for more technical control over query authoring.
• Row caps to control the maximum number of rows returned.
• AI-assisted SQL scaffolding when you want help getting started.

Together, these capabilities make the IDE a workspace for experienced users rather than simply a SQL text box attached to a chatbot.

An AI SQL assistant, without pretending SQL expertise is obsolete

The IDE also includes a lightweight AI experience.

A user can enter a simple request and use an LLM to create an initial SQL scaffold based on the data model.

But we've made an intentional distinction between this experience and Supper's main chat agent.

The assistant inside the IDE is there to help a technical user get started. The generated SQL is a scaffold: something you can inspect, modify, and build on.

For more open-ended agentic analysis, the full Supper chat experience remains the more capable environment.

That separation reflects how we think technical users actually want to work.

Sometimes you want an agent to take on more of the analytical process.

Sometimes you want AI to give you a head start and then hand you the controls.

Why use Supper's SQL IDE instead of a separate SQL IDE?

Standalone SQL IDEs remain useful tools. The problem is that they sit at arm's length from the rest of an agentic analytics workflow.

If an AI system generates a query and you need another application to inspect it, you have to move between environments. If you want to bring those edits back into the conversation, you have to move the context again.

Supper removes that boundary.

You can move from a conversation to the underlying SQL, work directly with the query, and then move back into the agentic experience.

Or you can start with SQL and use the resulting data to begin the conversation.

The advantage isn't simply having another place to write SQL.

It's having SQL and AI operate as parts of the same workflow.

Who is Supper's SQL IDE for?

The SQL IDE is designed primarily for sophisticated technical users who already know SQL and understand their organization's data model.

That can include data analysts, data administrators, and other technical members of a data team who want more direct control over retrieval logic.

For someone who would rather ask a business question and let an agent manage the technical details, Supper's conversational experience remains the natural place to work.

For someone who wants to inspect every join and tweak the query directly, there's now a workspace for that too.

The two experiences are complementary.

SQL and AI don't have to compete

The rise of conversational analytics has created a false choice.

On one side: SQL, built for technical precision and control.

On the other: AI agents, built for natural-language exploration and more open-ended analytical workflows.

We think modern analytics products should support both.

The right interface depends on the user, the task, and even the stage of the analysis.

A business user may begin with a question.

An analyst may begin with SQL.

The same analyst may ask an agent to explore what happens next.

And when the conversation produces an important query, they may want to open the SQL and make a precise adjustment themselves.

The future of analytics isn't chat replacing SQL. It's chat and SQL becoming two interfaces to the same analytical workflow.

That's what the Supper SQL IDE is built to enable.

FAQ

What is an AI SQL IDE?

An AI SQL IDE combines traditional SQL-development capabilities with AI assistance. In Supper, that means users can work directly with SQL while remaining connected to an agentic analytics environment. The IDE also includes lightweight AI assistance for creating an initial SQL scaffold.

Can I edit SQL generated by Supper?

Yes. SQL generated as part of Supper's data-retrieval workflows can be moved into the SQL IDE, where a technical user can inspect and modify it.

Can I start a Supper analysis with an existing SQL query?

Yes. Existing SQL can be used as the starting point for a workflow. The query and its returned data can then become the launchpad for a Supper conversation.

Does Supper's SQL IDE replace the chat experience?

No. The SQL IDE complements Supper's agentic chat experience. Chat is designed for more open-ended conversational analysis, while the IDE gives technical users more direct control over SQL.

Does Supper's SQL IDE generate SQL with AI?

Yes. The IDE includes a lightweight AI assistant that can help scaffold an initial SQL statement. It is intended as a starting point for technical users rather than a replacement for Supper's full chat agent.

What SQL IDE features are available in Supper?

The IDE includes table and column search, autocomplete, saved queries, access to previous SQL versions, multiple tabs, SQL dialect controls, configurable result-row caps, and lightweight AI-assisted SQL scaffolding.

Why use an integrated SQL IDE instead of a standalone SQL editor?

An integrated IDE makes it easier to move between query development and agentic analysis. Rather than copying SQL, results, and context between a standalone IDE and Supper, users can move directly between the SQL workspace and Supper conversations.