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.
Show and hide panes
Section titled “Show and hide panes”The buttons at the top right of a session show or hide one pane each:
- Terminal — the session’s terminal tabs
- Code — the code view
- Browser — the built-in browser
- Dev servers — the session’s dev servers
- Shared — files an agent shared
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.
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.
Show one pane alone
Section titled “Show one pane alone”⌥-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.
Each session keeps its panes
Section titled “Each session keeps its panes”The window remembers which panes each session had open, and which one had the keyboard. A session you have not opened before starts with the terminal alone.
Resize panes
Section titled “Resize panes”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.
Change the pane order
Section titled “Change the pane order”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.
Move the keyboard between panes
Section titled “Move the keyboard between panes”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 |
⌘1 to ⌘9 |
Ctrl+1 to Ctrl+9 |
Go to a 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.
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.
Keep a pane on the session in view
Section titled “Keep a pane on the session in view”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.
Pop a pane out into its own window
Section titled “Pop a pane out into its own window”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.
A pop-out window that follows
Section titled “A pop-out window that follows”⇧-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.
Where the main window opens
Section titled “Where the main window opens”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.