Workspaces and persistent sessions
Development reference · View source
Runyte runs in one of three modes. The status line names the one in use, and a session keeps its mode until it ends.
| Mode | Flag | Workspace | After the TUI exits |
|---|---|---|---|
| editor | --editor, or the runed command | None: edits files and directories anywhere | Gone |
| ide (default) | --ide | Yes, with Git, language servers, MCP, plugins, and terminals | Gone |
mux (ide+mux) | --mux, -a | Yes, as in ide, kept by a local host process, the persistent session | Kept: open and unsaved buffers, selections, registers, syntax state, diagnostics, Git projections, language-server processes, and terminal sessions |
The mode setting chooses the mode for launches that give no mode option; it
is ide unless set otherwise. The launch directory never changes the mode.
A workspace is one project directory and its editor scope: a Git
repository, or a directory holding the workspace state directory (.runyte/),
found by walking up from the launch directory. ide and mux need one. Outside a
workspace they refuse with
no workspace here; run runyte --init DIRECTORY to create one.
Persistent sessions work on Unix and Windows; see Windows support for the Windows differences.