Skip to content

Panes and windows

A session can show several panes side by side: the terminal, the code view, the built-in browser, its dev servers and the files its agents shared with you. Use panes to read a diff or check a page while the agent works in the terminal next to it.

The buttons at the top right of a session show or hide one pane each:

Click a button to show or hide its pane. At least one pane stays open. If you hide the last one, the terminal comes back.

Dev servers, shared files and the scratchpad open over the panes

Section titled “Dev servers, shared files and the scratchpad open over the panes”

You usually check the dev servers, the shared files and the scratchpad for a moment, so their buttons open them over the other panes instead of beside them. Click outside, press Esc or press ⌘W (Ctrl+W on Linux, ⌥⇧W in a browser) to close them again. The keyboard goes back to the pane that had it.

To keep one of them open beside the other panes, click the pin button at the top right of it, or use Pin the dev servers beside the panes, Pin the shared files beside the panes or Pin the scratchpad beside the panes in the palette. It then works like the other panes until you hide it, and the next click on its button opens it over the panes again.

⌥-click and ⇧-click on these buttons still act on the pane: they show it alone or make it follow the session in view.

While the dev servers, shared files or scratchpad are open over the panes, the built-in browser’s page is hidden, because the page draws above everything else in the window.

Some actions open a pane for you. Opening a file, a diff or a commit shows the code pane. Picking a terminal tab in the sidebar, the fleet view, the palette or a notification shows the terminal pane.

The palette has the same controls, such as Show code pane and Hide browser pane. ⌘⇧E (Ctrl+Shift+E on Linux) shows the code pane, or hides it and gives the keyboard back to the terminal.

⌥-click (Alt-click on Linux) a pane button to show only that pane. ⌥-click it again to bring back the panes it hid. The palette commands Terminal only, Code only, Browser only and Dev servers only do the same.

The right end of each pane’s tab strip has buttons that act on that pane:

Button Action
Window Moves the pane into a window of its own
Float Shows the pane over the other panes. Click it again to put the pane back beside them
Maximize Shows the pane alone, as ⌥-click on its button at the top right does. Click Restore to get the others back
Minimize Hides a floating pane. Its button at the top right shows it again, still floating
Close Hides the pane. A maximized pane brings back the panes it hid, and a floating pane stops floating

When a pane is the only one open, float, maximize and close are greyed out. A floating pane goes back beside the others when no other pane is open under it, and floats again when one opens.

⌘⌥↩ (Ctrl+Alt+Enter on Linux) floats the pane that has the keyboard, or puts it back. ⌘⇧↩ (Ctrl+Shift+Enter) maximizes it, or restores the panes. In the code editor ⌘⇧↩ inserts a line above instead, so use the button or the palette there. The palette has Float the pane, Maximize the pane and Close the pane, and the macOS Window menu has the same three items.

While another pane floats over the built-in browser, the browser’s page is hidden, because the page draws above everything else in the window.

The window remembers which panes each session had open, which one had the keyboard and which one floats. A session you have not opened before starts with the terminal alone.

Drag the separator between two panes to change their widths. mocante remembers the widths on this device for each set of open panes. A terminal and code split comes back as you left it, even after you had three panes open.

Drag the edge of a sidebar to change its width. This works on the sidebar with your projects and sessions, the git panel, the file tree and search panel in the code view, and the list in Settings. mocante remembers each width on this device.

To set a width with the keyboard, focus the edge with Tab, then press ← or →. To go back to the first width, double-click the edge.

Panes lay out left to right in one order, for every session and every window. The buttons at the top right follow the same order.

To change it, open Settings › Appearance › Pane order and drag the panes into place. The order syncs with your other settings.

One pane at a time has the keyboard: the one you last clicked. When more than one pane is open, a line along its top edge marks it.

Keys (macOS) Keys (Linux) Action
⌘⌥← / ⌘⌥→ Ctrl+Alt+← / Ctrl+Alt+→ Move the keyboard to the pane on the left / right
⌘⌥↩ Ctrl+Alt+Enter Float the focused pane, or put it back
⌘⇧↩ Ctrl+Shift+Enter Maximize the focused pane, or restore the panes
⌘1 to ⌘8 Ctrl+1 to Ctrl+8 Go to a tab of the focused pane
⌘9 Ctrl+9 Go to the last tab of the focused pane
⌘⇧[ / ⌘⇧] Ctrl+Shift+[ / Ctrl+Shift+] Previous / next tab of the focused pane
⌘T Ctrl+T New tab in the focused pane
⌘W Ctrl+W Close the focused pane’s tab

The tab chords act on the pane that has the keyboard. ⌘T opens a terminal tab in the terminal, a file browser in the code pane, or a new page in the browser. The dev servers pane and the shared pane have cards, not tabs, so there ⌘W hides the pane, and the other tab chords do nothing. In the scratchpad, the tab chords act on its notes, also while it is open over the panes: ⌘T starts a new note in a tab, ⌘W closes the note’s tab, and ⌘W on the last tab hides the scratchpad.

A diff that an agent opens in the code view shows the code pane, but the keyboard stays where it was, because the agent usually waits for your answer in the terminal.

Usually a pane belongs to its session. You can make a pane follow you instead: it stays open as you move between sessions and always shows the session you look at.

  • ⇧-click (Shift-click) a pane button to make that pane follow. ⇧-click it again to stop.
  • Or use the palette, for example Keep the code pane on the session in view.

Hiding the pane also stops it following.

You can move a pane into a window of its own, for example to put the code view on a second monitor.

  • Click the button at the right end of the pane’s tab strip.
  • Or use the palette: Open the terminal in a new window, Open the code pane in a new window, Open the browser in a new window, Open the dev servers in a new window or Open the shared files in a new window.

The pane moves; it does not show in both windows. The main window shows the panes that remain. If every open pane is away, it shows a button to bring one back.

The pop-out window has a slim title bar that names the session and the pane. Its tab chords, the palette and the git commands work as in the main window, and the session chords move it to another session. The code pane keeps its open tabs and unsaved text when it moves in either direction.

To bring the pane back:

  • click Back to the main window in the pop-out, or
  • pick Bring the terminal back to this window (or the same for the code pane, browser, dev servers or shared files) in the palette.

If you close the pop-out with its own window controls, the pane closes in the main window too. Its tabs stay, and come back when you show the pane again.

In a pop-out, ⌘W closes a tab of its pane and the last tab closes the window. For the terminal, ⌘W closes the window at once, because the last terminal tab cannot close without ending the session.

The main window keeps the notifications. A diff that Claude Code proposes while the code pane is away opens in the main window.

⇧-click the pop-out button, or pick Open the code pane in a window that follows (or the terminal, browser or shared files version) in the palette. The window then shows that pane for whichever session the main window shows. Its title bar says Following.

When you pick a session in a window that follows, the main window moves to it too, so both windows stay on one session.

The main window opens where you closed it, at the same size, and maximised if it was. If the monitor it was on is gone, it opens on a display you have. If it is now too big for its display, it shrinks to fit.