What is Studio?
Marimo Studio turns one saved Marimo notebook into named web views. The notebook owns data, Python computation, controls, and reusable results. Each view owns the layout, wording, visual encoding, and browser interaction for one job.
Building occupancy
A reactive scope updates one room-sensor model across a live monitor, model review, and A4 field report.
The Building occupancy notebook supports a live monitor, a model review, and a printable field report. All three views use the same sensor analysis. Each has its own source documents, browser dependencies, build, route, and current artifact.
The product model
saved Marimo notebook
-> named view
-> view project
-> built artifact
-> Preview with notebook resultsA view is the stable name and URL, such as monitor, model-review, or pdf-report. Its view project is the saved frontend directory. A view provider inspects that project and builds an immutable browser artifact. Studio combines the artifact with a notebook runtime to create the presentation shown in Preview.
The notebook and each view can change independently:
| Action | Result |
|---|---|
| Save notebook code | Marimo reruns affected cells and updates mounted results |
| Save a source document | Studio builds a new artifact for the selected view |
| Switch views | Studio presents another artifact against the same notebook |
| Switch runtimes | The same artifact receives results from another notebook runtime |
A failed build keeps the last successful artifact available while Source shows the diagnostic.
Notebook results enter the view by name
View source can place a complete cell, render one Python object, or read a browser value:
<marimo-cell name="summary"></marimo-cell>
<marimo-output value="chart"></marimo-output>
<strong mo-value="metrics.total"></strong>Studio resolves each target to the notebook cell that produces it and the upstream cells required to compute it. Marimo keeps control changes and dependent results reactive while the frontend stays mounted.
Place notebook results in a view explains the three projection forms.
Studio connects three authoring surfaces
- Notebook edits Python and reactive computation.
- Source edits the selected view project's source documents.
- Preview renders the current artifact with live notebook results.
Notebook and Preview open side by side beneath a thin toolbar. The source action opens the view editor beneath Preview. The native agent sidebar remains available as you switch views and focus the result.
Create your first view for a working path from a saved notebook. Why Studio? explains the product decision behind the model.