Sessions
A session is the studio as you left it: the records in the data panel, the open tabs with their selections, and the files already on the runner. With the local runner connected, the session this tab holds is saved to the runner as you work, and comes back when you open sigscape.org again.
Where it lives
Sessions are files in the runner's workspace, sessions/<id>.json. Nothing about a session reaches sigscape.org. Without a runner, the studio keeps its state in the browser tab only, as before.
One tab, one session
Each browser tab holds one session, like a notebook tab in Colab. The session's name sits in the studio bar; click it for the menu:
- New session starts a blank one in this tab; the one you were in stays saved.
- Rename this session, or double-click the name.
- The saved sessions, newest first, with when they were saved and how many records they hold. Open one here, or in a new browser tab.
- Delete forgets a session's records. Files and runs in the workspace are not touched; they belong to the workspace, not to a session.
Opening sigscape.org with no session in the tab loads the most recently saved one. /?session=<id> opens a particular one.
What is and is not in a session
| In the session | Not in the session | |---|---| | parsed records (what the data panel shows), tabs, selections, view settings | the bytes of files you dropped: those are uploaded to the runner the first time a tool needs them, and the session remembers where | | which uploaded file belongs to which record | runs: those are the runner's job list and show for every session that uses the same records | | the name of the session | the runner connection itself (the browser keeps that) |
A record whose file was never sent to the runner, reopened in a new browser, lists as before but has no bytes behind it; a tool that needs them says to add the file again.