Studio

What Studio is

A coding team you talk to — and where your code actually runs.

About 4 minutes

Studio is a team of coding agents you brief in conversation. They write and run real code, in a real repository, on a machine you control.

The thing to understand first

Your code runs on your host — your desktop app, or a cloud host you provisioned. Not in an opaque sandbox. The files are on that machine's disk; you can open them in your own editor while agents are working on them.

That single fact explains most of Studio's behaviour, including why nothing works until a host is online.

What you get

  • Agents that plan, write, run and fix code
  • A live preview you open in a real browser
  • A connected repo — GitHub, GitLab or Bitbucket
  • One-click deploy to Render or Vercel
  • Per-project integrations, environment variables and model routing

Steps

  1. Make sure a host is online — desktop or cloud.
  2. Open Studio and create or import a project.
  3. Describe what you want built. Start with the outcome, not the file layout.

You're done when a project exists and its preview runs.

Gotchas

  • No host, no Studio. Every operation needs somewhere to run.
  • It is a real codebase, not a toy. You can take it and run it anywhere.

Checked against

  • endpoints/studio/projects/
  • docs/STUDIO_BUILD_MODE_HOST_CONTRACT.md