Appearance
Separate desktop windows
The native Clusto desktop app can move a terminal session, note, or chat into its own operating-system window. This is useful for arranging work across monitors, keeping a reference note beside a terminal, or following a chat while using another part of Clusto.
This option is available in the native desktop apps (Windows, Linux and macOS). It is not shown in the web client or on mobile.
Open or focus a window
- Terminal session - open the pane actions menu, a session's menu in the Terminals tree, or the session row in the Sessions view, then choose the separate-window action.
- Note - open the active note's actions and choose the separate-window action.
- Chat - open the chat row's context menu or the active chat's actions, then choose the separate-window action.
- F1 command palette - search for the matching separate-window command for the focused terminal, open note, or active chat.
Clusto keeps one separate window for each resource within its connection and node scope. If that window already exists, using the action again focuses it instead of opening a duplicate.
The original view becomes a compact placeholder while its resource is open in another window. Use the placeholder's focus action to bring that window to the front. Closing the separate window returns the full view to the main window.
Tear out a layout or a node
Besides single resources, a whole workspace can move into its own window (desktop only).
- Pane layout - in the Terminals workspace, open the pane actions menu and choose Move layout to new window, press
Ctrl+Shift+O, or run the same command from theF1palette. The current split, with its live terminals and chats, opens in a new window and the main workspace is left with an empty pane. - Node - in a cluster with more than one node, right-click a folder in the Terminals tree and choose Open (node) in new window, or search the
F1palette for it. The window shows that node's sessions in its own Terminals tree next to its own workspace. Layouts whose sessions all run on that node move into the window with it; layouts that mix nodes stay in the main window.
A torn-out window keeps its navigation to its own slice: the layout, or the node's tree and workspace. Splitting, the pane actions menu, the session picker, new sessions and chat panes work as in the main window.
A session shows in one window at a time. In the main window, a session that a torn-out window shows becomes the placeholder, and choosing it in the Terminals tree brings that window to the front and shows the session there. For a node window this covers every session on that node.
Move it back
Use Move back to main window in the window's header or its pane actions menu, or press Ctrl+Shift+O in that window. Its layouts return to the main workspace, the active one is shown, and the window closes.
Closing a torn-out window with its close button discards only its arrangement: the sessions keep running and stay in the main Terminals tree.
After a restart
Torn-out windows that are still open when Clusto exits come back on the next start, at the same position and size, once the main window has connected to the same profile. A position on a monitor that is no longer attached falls back to the default placement. A window you closed or moved back is not restored.
Connection ownership
The main Clusto window owns the daemon connection and account context. Separate windows reuse its current profile, connection state, and session list rather than opening another authenticated connection. Tokens and other connection secrets are not copied into a child window.
If the main connection drops, a separate window shows the disconnected state. Reconnect from the main window and the separate window resumes automatically. Closing the main window also closes every separate window it owns.
Windows are scoped by connection profile and, where relevant, node. This keeps the same terminal, note path, or chat identity from being confused with a resource reached through another saved profile or direct connection.
Notes with unsaved changes
When the active note has local edits, Clusto saves it and waits for the daemon to confirm the write before opening the separate editor. If the save fails or conflicts, the note stays in the main window and the separate window does not open. This prevents two editors from starting with different versions of the same note.
The separate Notes editor does not overwrite the main window's remembered tab list, active note, or preferred serving node.
Sessions run as another Windows user
When a Windows node starts a session as another account (see Session Credentials), a helper hosts the terminal for that account. Pressing Escape in such a session is now sent to the program at once; earlier versions held it for about 50 ms, which made Escape in editors and agent prompts feel slow.