Cherry Pi has two desktops: a terminal TUI and Cherrytop, its web GUI. Both give you a multiplexer for working with several panes at once. The terminal desktop puts project layers, tiled panes and draggable floats within reach of the keyboard. Cherrytop brings apps and live terminals into the browser, with a canvas underneath its tiled layout.

You can use an editor beside a running test, keep Picache in view while you review a change, or open an app beside the terminal serving it. The two interfaces have their own arrangements. They reach into the same workspace without requiring every window to occupy the same place in both.

The terminal desktop

The Cherrytree at the left shows where the current workspace sits and which layer or surface is in front. A layer holds a project’s working view. Expand its branch to find its panes; select the layer to bring its work forward. An API project can keep its shell, editor and checks together while you work on the website in another layer.

Switch back and the shell is still in its folder, with its output on screen. The terminals you left behind keep running. You do not have to rebuild the arrangement each time you change tasks.

A project in the terminalThe tree locates the active layer. A floating tool sits above tiled panes.A project in the terminalCherrytreeWorkspace → API layerAPI layerTiled deskEditorProject filesTerminalRunning checksFloating logSame running pane WorkspaceAPI layerEditorChecks
The tree shows where a pane belongs, even when it floats.

Tiles when you need order, floats when you need room

Keep your editor and shell in tiles, splitting the available space between them. A log you need to consult occasionally can become a floating window. Drag it by the title, resize it from an edge and dock it again when you want it back in the layout. Moving the pane preserves its running program.

Cherry Pi includes an editor pane, so opening a file does not require leaving the desktop. Your own terminal tools can sit alongside it. The Cherrytree keeps track of where each pane belongs, including the ones you have lifted into floats.

Cherrytop: a multiplexer over a canvas

In the browser, Cherrytop gives you tiled panes for the task in front of you and a canvas for arranging work across a larger space. Tile an app beside its terminal, or put Picache chat next to the code. Under that layout, you can pan and zoom among windows, widgets, frames and named spaces.

Two views in CherrytopA tiled multiplexer sits over a pannable canvas.Two views in CherrytopCanvas underneathPan, zoom and revisit named spacesTiled work in frontBrowser multiplexerApp previewLive terminalAnother spaceWindows and widgets PAN TO A NAMED SPACE
Tiling arranges the current task. The canvas gives it a place to return to.

This gives the GUI two ways to work. Stay in splits while editing or checking an app. Pull back to the canvas to find another group of windows, then move into that space. A named space gives you somewhere recognizable to return to.

An app beside its terminal

A served app and its terminal make a useful pair. The app shows what a user would see; the terminal holds the output you need when something behaves unexpectedly. For editing, editor.pi provides Cherry Pi’s web GUI editor.

With local names installed, https://cherry.pi opens the workspace. A served app can have its own local address. Cherrytop can also attach to an existing terminal run, so a browser window can show work already running on the host. Its layout remains independent of the terminal desktop’s pane arrangement.

Durability across views

The running terminal and the window displaying it have separate lifetimes. Terminal runs live outside the desktop client: close the client and reconnect to a run when you reopen it. Cherrytop attaches through Sakura, starting with a screen snapshot and then following the live stream. That persistence covers client exits and reconnects; recovering a terminal after a machine reboot is a separate concern.

The workspace also keeps durable conversation history and run records in SQLite. For changes Cherry Pi governs, it records intent before execution and the result afterward. If a write is interrupted and its outcome is uncertain, Recovery gives you a place to settle what happened before trying again.

Working with Picache and other agents

Picache has its own chat, and an installed agent harness can have its own pane. Keep an agent’s work beside the diff you are reading or the checks you are running yourself. When agents exchange a question or a handoff through the workspace, they can refer to a branch or path you can inspect in the project.

These arrangements can be scripted, too. Controlling the TUI and Rex with Lua shows how to manage panes programmatically, including a Cherry Pi desktop running inside Rex.

For the spatial navigation experiments, continue with Cellar Door, The Infinite Canvas and Traverse the Network.