---
title: ".bloom* studio"
description: >-
  Open a project on a pannable canvas, launch tools as windows, and fill in
  their parameters yourself. Studio is experimental.
tags:
  - studio
---

Studio opens one project on a pannable canvas. You launch each tool as a window, fill in its form, and run it. Chat and the CLI send jobs to the same backend, but in Studio nothing routes the work for you: you pick the tool and set every parameter.

> **Studio is experimental**

> The first time you open a Studio page in a session, a dialog warns that the workspace is still in active development. It is meant for testing: features may be incomplete, may change without notice, and may lose data. **Continue to Studio** acknowledges the warning until you reload the page.

## How you get there

Studio has no entry in the main navigation. You open it from a project's campaign:

- In **Files**, open a project and select a campaign, then choose **Open Studio**. This loads `/studio/<project-id>/<campaign-id>`.
- `/studio/<project-id>` opens the project without a campaign.
- Once a project has a slug, the address bar is rewritten to `/<username>/<project-slug>`.

You must be signed in. No plan tier or feature flag gates Studio. The browser window must be at least 1024 px wide.

## What is on screen

| Region | What it holds |
|---|---|
| Left sidebar | **Back to Projects**, usage remaining this month, the project's name and description (both editable), members and referral codes, and **Data Sources** shortcuts. The shortcuts do nothing yet, so use the toolbar's **Data Sources** menu |
| Canvas | A pannable, zoomable surface that holds the windows. See [Canvas](/docs/studio/canvas) |
| Bottom toolbar | Menus for files, data sources, window layout, tools (**Model**), burst!, quick actions, jobs and reports, tool settings and help |
| Right sidebar | **Pipeline**: active jobs, the next step and the drug-development checklist. **Workflows**: your saved and shared workflow templates. **Files**: does not load inside a project yet |
| Top right | The **chat / studio** mode toggle |

Both sidebars collapse with their chevron buttons.

## How Studio relates to Chat

- **Jobs use one service.** Studio submits jobs to the same service as Chat and the CLI, and it lists the jobs recorded against the open project.
- **Results render differently.** Chat renders results as tiered [canvas cards](/docs/chat/canvas). Studio has no card grid: a result opens inside the tool window that ran it, or in a **Job Details** window.
- **The chat toggle stays in Studio.** Inside Studio, choosing **chat** on the mode toggle opens a **batch planner** window on the canvas instead of leaving the page. The planner is a plain language-model conversation that drafts parameter sweeps and multi-step plans. It does not call tools or submit jobs.

To run a full conversation that can call tools, open [Chat](/docs/chat).

## Pages in this section

## Read next