Create and manage views
A view is the stable name and URL for one interface backed by a notebook. Add a view when the same analysis needs a different layout, explanation, interaction, or audience.
The Rio 2016 athletes example has overview, explorer, and field views. Each view has its own project, build, and last successful artifact. Keep shared measures and reusable controls in the notebook, and layout, wording, and browser dependencies in each view.
Create another view
Open the view menu and choose New view. Enter a lowercase name, choose a starter, and inspect Files created before confirming. Studio saves pending Source edits before switching to the new view.
The equivalent command is:
marimo-studio view create report --target analysis.pySet the default view
The default view opens at the main route, /. The report view opens at /report/. Serve report at / with:
marimo-studio view default report --target analysis.pyStudio stores the choice as default in the notebook configuration:
[tool.marimo-studio]
default = "report"Rename a view
Rename a view to give its URL and menu entry a new name:
marimo-studio view rename report summary --target analysis.pyThe project keeps its source, artifacts, and build history, and a default view stays the default. The view reads as stale until its next build, which republishes it under the new name. Links to /report/ stop resolving, so update any view that links to the old URL. While Studio serves the view, rename it as described in Change a served view.
Switch views
Choose a view from the view menu. Studio keeps the active Python runtime session connected, so controls and computed results retain their current state. Each Browser runtime view uses its own browser notebook instance.
If Source has pending edits, Studio saves them before the switch. A failed save or unresolved source conflict keeps the current view selected for repair.
Remove a view
Use the remove action beside a view name and confirm with Remove. Removal permanently deletes the view project and its files. If the removed view was the default, Studio names the replacement in the confirmation and promotes it to the main route.
Studio keeps at least one view. Create a replacement before removing the last one.
The terminal command follows the same contract:
marimo-studio view remove report --target analysis.pyChange a served view
A running Studio server keeps the artifacts of the views it serves in use. marimo-studio view rename and view remove then report view-in-use with that server's process ID. Rename or remove the view from code mode in that notebook, or remove it from the Studio tab, so the server releases its artifacts first.
Use Choose a frontend to select a starter. Use Navigate and preserve state when views link to one another or share public query state.