Introducing Kubb Studio
Tuning a Kubb config takes repeated runs. You change a plugin option, run kubb generate, and check the output folder.
Kubb Studio puts that loop in a browser tab. You change plugin options, generate, and review the resulting files. Connect your project to run Kubb locally, or use the shared sandbox to try it without setup.
Generation stays where your agent runs
With a connected CLI or Docker agent, Kubb uses the spec and plugin versions in your environment. Studio receives plugin settings, the project path, progress, generated file paths, and file hashes. Your local spec is not uploaded. During an interactive generation, Studio receives generated file contents only when you grant read access.
One command to connect
The runtime ships with the CLI, so a project with Kubb installed needs nothing extra:
kubb studioThe first run in a project asks you to approve a pairing code in Studio. Later runs in that project connect straight away.
Choose what Studio can access
A session with no permissions granted generates in memory. It sends progress and file paths to Studio but does not write to your output folder. The agent still keeps copies of recent generations in node_modules/.cache/kubb. The CLI asks about five permissions:
| Permission | What it grants |
|---|---|
--allow-read | Studio can read the source of the files a generation produced. |
--allow-read-ast | Studio can read the parsed spec (the Kubb AST). |
--allow-write | Generated files are written to your output folder. |
--allow-config-edit | Studio may change plugin options in your kubb.config.ts. |
--allow-exec | The formatter, the linter, and output.postGenerate run as child processes. |
The CLI remembers your answers per project. In CI or without a TTY, it does not prompt, so pass the needed permissions as flags.
Editing config from the browser
With --allow-config-edit, Studio can save changed plugin options to kubb.config.ts. The edit preserves the surrounding comments and formatting.
Beyond your laptop
The kubblabs/kubb-agent Docker image keeps a team agent connected. In CI, kubb studio snapshot publishes an installable package for a pull or merge request. It takes no permission flags and uses an organization CI API key. See the guide for setup.
Try it
Studio is live at kubb.studio. The guide walks through connecting a project, and the kubb studio reference lists every action and flag.