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 Windows and Linux apps. 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.

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.