Cherrytop is both a multiplexer and a canvas in the browser. Tile panes to work side by side, with an app beside its terminal or Picache chat next to the code. Under that arrangement is a canvas you can pan and zoom, with windows, widgets, frames and named spaces.
The tiled view gives the work in front of you a layout. The canvas gives that work a place in a larger arrangement. You can spend a session in splits, then pull back to find another group of windows and return to it when you need it.
From tiled panes to the canvas
If the recording opens an existing terminal run, look for the output already there. Cherrytop can attach to that run in a browser window. It keeps its own arrangement, so opening the terminal here doesn’t require the browser to copy the terminal desktop’s pane layout.
Terminal persistence matters in the GUI, too. A Cherrytop window attaches through Sakura to a run on the host. When you reopen the view, Sakura starts with a screen snapshot and follows the live stream. The workspace’s durable run records and conversation history are kept separately from the browser view.
An app beside its terminal
A good way into the browser desktop is to open something you’re already working on. Tile an app beside its terminal. The app shows what a user would see. The terminal gives you somewhere to look when the app behaves unexpectedly. If you need to edit a file, editor.pi is available in the GUI.
With local names installed, https://cherry.pi opens the workspace. A served app can have its own local address.
See The Cherry Pi TUI for the terminal side, where the Cherrytree shows the active layer and panes. The two posts show different ways to arrange and reach work in cherry π.
Continue with The Infinite Canvas and Traverse the Network for the experiments in spatial navigation.