Appearance

Edit and preview in Studio ​

Studio adds a toolbar to marimo edit in any environment that contains marimo-studio, including for a new, unsaved notebook. Getting started opens a notebook and adds its first view.

Use the toolbar ​

Studio opens Notebook and Preview side by side. The native agent sidebar remains available, including when you focus the view.

  • Show notebook only focuses the notebook. Click Show view beside notebook to restore the split, including its Source pane and sizes.
  • Edit view source opens Source beneath Preview. File tabs select the view's authored documents.
  • Live (or the current status) gives a short runtime state. Hover or focus it for a contextual summary. Click it for diagnostics and runtime choices.
  • Workspace options contains focus commands and Open preview in new tab.

Arrange the workspace ​

Drag a divider to resize. Choose Arrange panes from Workspace options to expose each pane's placement, swap, and close controls. Pane headers remain hidden during normal editing. The menu also offers Equalize split sizes, Open saved layout, and Restore workspace.

Studio saves the custom layout for each notebook and selected view in the current browser. Open saved layout returns to that arrangement.

When the available width or height cannot fit the panes, use the Visible surface selector to choose Notebook, Source, or Preview.

Save and build ​

Source saves the active document and rebuilds the selected view. The build status reports:

  • Building while a replacement artifact is being prepared
  • Up to date when Preview matches saved source
  • Build needed when saved source has changed
  • Build failed when the latest attempt reported an error

Preview stays on the last successful artifact while another build runs. A failed build keeps that artifact visible and puts the repair diagnostic beside Source.

Use an explicit build after another editor, coding agent, or CI process changes the project:

console
marimo-studio view build dashboard --target analysis.py

Choose a runtime ​

Click the status item in the toolbar to choose where notebook code executes:

  • Python runtime uses the editor's Python session and can access local files, databases, installed packages, and server credentials. Its configuration ID is server.
  • Browser runtime starts a notebook in a browser worker. The browser receives notebook source and must reach its dependencies and data. Its configuration ID is wasm.

Switching runtimes keeps the view artifact fixed and replaces the notebook runtime that supplies results.

Use Open preview in new tab to inspect the current presentation without the authoring panes. Create and manage views covers switching between views. Continue with Manage view source for the Source catalog and conflict recovery.