The workbench for Looker and Dataform.

Why this exists

Doesn't the Dataform cloud IDE already do this?

Parts of it, well. Auto-compile as you type, run a single object, results right under the code. But it lives in a browser tab, blind to the coding agent doing the writing, and it stops where Looker begins.

Doesn't Dataform have AI built in?

It ships with Gemini, which offers itself at every turn and can't see past Dataform's walls. It knows nothing about your Looker project, the half of the pipeline your warehouse exists to serve. Graver's answer is different: bring the agent you already trust, and let it see everything.

And the Looker IDE?

Open a second file and the first one closes. Drag-and-drop reports can't be version-controlled, and LookML has almost no tooling around it. It isn't where real work can happen.

Why one app for both?

Because it's one pipeline. The warehouse code exists to feed the reports, and the reports break when the warehouse changes. A change is only correct when both sides agree, so the tool should see both sides.

Where does the coding agent fit?

It writes most of the code now; the editor is where you read. What the agent lacks is eyes: a way to compile, validate, run, and see what happened. Graver gives the agent the same workbench it gives you.