Terminals and tabs
Every session in mocante is a tmux session, and every tab is a real terminal
in it. Full-screen programs such as agent CLIs, editors and htop work as in
any terminal, and your work keeps running when mocante is closed.

Sessions survive restarts
Section titled “Sessions survive restarts”tmux holds the session on the host, not mocante. You can quit the app, close the laptop or lose the SSH connection, and the programs in the session keep running. When mocante connects again, it shows the session as you left it.
To attach to a session from another terminal, right-click the session and pick Copy attach command, then paste the command into your own terminal. The session name in it is quoted for the host’s shell and again for yours, so the command runs as it is when both shells are sh, bash, zsh or dash.
A reboot of the host or a crash of the tmux server ends the sessions. See Restore sessions after a reboot.
Work with tabs
Section titled “Work with tabs”The tab strip above the terminal shows the session’s tabs. An agent tab has a status dot. A tab where mocante detected an agent in a shell has an auto badge.
| To | Do this |
|---|---|
| Open a shell tab | Click + at the end of the strip, or press ⌘T (Ctrl+T on Linux). |
| Close a tab | Click its ×, or press ⌘W (Ctrl+W). |
| Reopen a tab you just closed | Click Undo in the notice, or press ⌘⇧T (Ctrl+Shift+T). |
| Go to a tab by position | ⌘1 to ⌘8 (Ctrl+1 to Ctrl+8). ⌘9 goes to the last tab. |
| Go to the previous or next tab | ⌘⇧[ and ⌘⇧] (Ctrl+Shift+[ and Ctrl+Shift+]). |
| Rename a tab | Right-click it and pick Rename tab…. |
A closed tab keeps running, out of sight, for five seconds. If you reopen it in that time, it comes back in its old place with everything that ran in it, such as an agent in the middle of a turn. After five seconds mocante ends it.
⌘W does nothing on the last tab of a session. To end the session, use
Close session… from the session’s right-click menu. The host must be
connected: mocante ends the tmux session first, so that a session it could not
reach does not come back on the next scan. If tmux cannot end it, the session
stays and you see why. If you also asked to remove the worktree and delete the
branch, and git keeps one of them, the session still closes and you see what
stays and why.
When a session is no longer in mocante, the view shows Session ended. and the reason:
- The host is not connected.
- The host is no longer in mocante.
- The workspace is no longer in mocante. Its tmux session can still run on the host.
- The session stopped on the host.
- The host does not have this session.
Start again makes a new session on the same branch (or with the same name). It shows only when the workspace is still in mocante and its host is connected. Close goes back to the workspace, or to the fleet page when the workspace is gone. In a pop-out window, Close closes the window.
When you switch tabs, the keyboard moves into that tab’s terminal, so you can type at once.
Move between sessions
Section titled “Move between sessions”| Keys (macOS) | Keys (Linux) | Action |
|---|---|---|
⌘⌥↑ / ⌘⌥↓ |
Ctrl+Alt+↑ / Ctrl+Alt+↓ |
Previous / next session |
⌃1 to ⌃9 |
Alt+1 to Alt+9 |
Session by its place in the sidebar |
⌘[ / ⌘] |
Alt+← / Alt+→ |
Back / forward through places you visited |
The session name in the header opens a list of the other sessions in the same workspace. Switch session in this workspace… in the palette does the same.
Move a tab to another session
Section titled “Move a tab to another session”A tab can move to another session on the same host. The program in it keeps running, and the tab keeps its name and its scrollback.
- Right-click the tab and pick a session under Move to session. Sessions in the same workspace come first.
- Or run Move to session… from the palette for the tab on screen.
- Or drag the tab, from the tab strip or the sidebar, onto another session in the sidebar. Drop it on the session row to put it last, or on one of that session’s tabs to put it next to that tab.
The last tab of a session cannot move, because tmux ends a session that has no tab left. A tab cannot move to a session on another host, or while its host is offline. If the tab was on screen, the view follows it to its new session. The other session keeps showing the tab it showed before.
A moved tab keeps some ties to the session it came from:
- Approvals. An agent in the tab does not get the approvals you gave the new session. It asks again, and Allow for the session then covers that tab only.
- IDE. A Claude Code in the tab stays connected to the IDE of the session it came from. Its diffs open there, and the connection ends when that session closes. To link it to the new session, start Claude Code in a new tab of that session.
Reorder tabs, sessions and projects
Section titled “Reorder tabs, sessions and projects”Drag to reorder. A line shows where the item will land.
- Tabs: drag a tab in the tab strip, or under its session in the sidebar. Or right-click it and pick Move left or Move right.
- Sessions: drag a session row to a new place under its workspace. Or right-click it and pick Move up or Move down.
- Projects and workspaces: drag a project header, or use Move up and Move down in the right-click menu.
The order of projects and sessions syncs to your other devices.
More workspaces
Section titled “More workspaces”When a project has two or more workspaces with no session in the sidebar, they fold into one More workspaces row at the end of the project. Click the row to show or hide them. A project with only one empty workspace shows it in its usual place.
A workspace counts as empty when all of its sessions are in Favorites or Settled, because none of its sessions show under it. The row opens by itself while one of its workspaces is on screen.
Read a session row
Section titled “Read a session row”Each row in the sidebar says what the session works on. The first line is the first of these that the session has:
- the name you gave it with Rename session
- the title the agent gave its task
- the title of the issue it started from
- the start of the first prompt
- the title of its pull request
- its branch
When something other than the branch is on the first line, the branch moves to
the second line. The second line also shows how long the session has been in
its state, such as Waiting 18s.
When the branch has an open pull request, its number and health show at the
end of the first line, such as #212 ✓.
The prompt text stays on this device. It does not sync to your other devices, and agents cannot read it through mocante’s tools. mocante keeps the first 80 characters and leaves out a word that looks like a token.
Favorite sessions
Section titled “Favorite sessions”Star the sessions you come back to most, and they move to a Favorites section at the top of the sidebar.
- Hover a session row and click the star, or right-click the session and pick Add to favorites. Do the same to remove it.
- A favorite leaves its workspace while it is starred. Its row shows its project and workspace below its name.
- Drag a favorite to reorder the favorites, or use Move up and Move down.
- The shortcuts that jump to a session by its place (
⌃1to⌃9, orAlt+1toAlt+9on Linux and Windows) and the next and previous session shortcuts count the favorites first, in the order the sidebar shows them.
Favorites and their order sync to your other devices. A favorite stays when you rename its session, and when its session stops because tmux or the host restarted: start a session under the same name and it is a favorite again. Closing the session removes the star.
Close a session
Section titled “Close a session”Close session… asks first, and you can choose to also remove the worktree and
delete the branch. After you confirm, the row leaves the sidebar and a toast offers
Undo for five seconds. Nothing is stopped or deleted until those seconds end.
⌘⇧T (Ctrl+Shift+T) also undoes the close, if it was the last tab or session
you closed.
When you close the session on screen, mocante shows another session of the same workspace: the one you looked at last, or else the next one in the sidebar. A workspace with no other session sends you to the next session in the sidebar.
Closed sessions go to Recently closed at the bottom of the sidebar, which holds the last 20 on this device. Start again makes a session with the same name and branch, with its tabs as you left them (see How a session comes back). If the close deleted the branch, the branch comes back at its last commit, and uncommitted work does not. If a tab does not come back, the session still opens with the others, and a notice says how many did not. Start a closed session again… in the command palette does the same.
Restore sessions after a reboot
Section titled “Restore sessions after a reboot”When the host reboots or its tmux server stops, the sessions on that host end. Your worktrees, branches and commits stay on disk, and so do the agents’ conversations. The next time mocante reads the host, a strip at the top of the sidebar says how many sessions stopped with tmux.
- Restore all makes each session again with its name and branch, in its worktree, with its tabs as they were (see How a session comes back).
- Open the strip to see the sessions. Restore brings back one session, and × removes one from the list.
- Dismiss clears the list.
Restore the sessions that stopped with tmux in the command palette does the same as Restore all, and Dismiss the sessions that stopped with tmux does the same as Dismiss. Start a closed session again… lists these sessions too, marked “stopped with tmux”.
If a tab does not come back, the session still comes back and stays on the list with that tab, so Restore tries it again.
A session that runs again on its old branch, because another device restored it first or you made it yourself, leaves the list, and a restore opens it as it is. A numbered session stays on the list even when a new session takes its number, and a restore gives it the next free number.
Only sessions with a running agent in them go on the list. A session of plain shells has nothing to resume, so make it again from the sidebar.
Your devices share the list. A session that you restore or remove on one device leaves the list on all of them. While one device restores a session, the others do not start it a second time. The list holds up to 100 sessions, apart from Recently closed, which stays on each device.
How a session comes back
Section titled “How a session comes back”Start again and Restore both make each tab again, in order:
- An agent that was running starts again and resumes its conversation if the agent can. If another open session already runs that conversation, the tab comes back as one you can resume, so the conversation does not run twice.
- An agent you had quit comes back as a shell tab with Resume, so nothing starts that you had stopped.
- A server your project declares starts again in its own tab. A server mocante only recognized comes back as a shell tab, since it has no command to run.
- A plain shell tab comes back empty, in its folder. What ran in it does not.
Inbox mode
Section titled “Inbox mode”The sidebar can show one flat list in place of the project tree. Select the inbox button at the top of the sidebar, or run Sidebar: inbox from the command palette. Run Sidebar: project tree to go back.
The list groups sessions by what they ask of you: Needs you, Done, Working and Idle. The longest wait goes first in Needs you. In the other groups, the most recent change goes first. Each row names its project and workspace. The session shortcuts follow this order, and you cannot drag a row to a new place.
This setting applies only to this device.
Settle or snooze a session
Section titled “Settle or snooze a session”When you are done with a session but want to keep it running, right-click it and choose Settle session. It moves to the Settled section at the bottom of the sidebar, and its terminal, agent and worktree stay as they are. A toast offers Undo for five seconds.
Snooze session… does the same for a time you pick: an hour, three hours, until tomorrow morning or until Monday morning.
The Settled section is one list for all your projects, newest first. Each row names its project and workspace, and on the right when its snooze ends, or Merged if it settled by itself after its pull request merged.
A session comes back to the list by itself:
- A settled session comes back when an agent in it starts work or needs input.
- A snoozed session comes back at its time. While an agent in it needs input, or waits for an approval, it shows on the list and then goes away again. Work alone does not show it.
- If you snooze a session that already needs input, the snooze covers that question. A new one shows the session.
- To bring one back yourself, right-click it and choose Return to the list.
A session in its own worktree also settles by itself when its pull request merges, if nothing runs in it, it has not failed, it has no star, and its worktree has no uncommitted files or commits after the merge. mocante reads this while a window is open, so it can take a few minutes. If you bring such a session back, it does not settle again for that pull request. To keep every session on the list, turn off Settle sessions when their pull request merges in Settings.
A settled or snoozed session keeps running: its agent, and the memory the agent uses, stay as they are. To free that memory, choose Stop agent, or close the session.
Settled sessions and snoozes sync to your other devices, the same way as favorites.
Rename a session
Section titled “Rename a session”Right-click the session and pick Rename session…, or pick it in the palette.
Copy, paste and links
Section titled “Copy, paste and links”- On macOS,
⌘Ccopies the selection and⌘Vpastes. On Linux,Ctrl+Cstays the terminal’s interrupt, so use the right-click menu to copy and paste. - The right-click menu also has Select all and Clear scrollback.
- Click a link in the terminal to open it. With the Ghostty renderer, hold
⌘(Ctrl) as you click. A link that a program set with its own text (OSC 8) asks first, because the text can differ from where it goes. Every link opens the way links from sessions do. - A paste loses control characters other than tabs and line breaks, so text you paste cannot end a paste early and run what follows as commands.
- A program on a remote host can copy text to your clipboard (OSC 52). mocante never lets a program read your clipboard.
Shift+Enterinserts a new line in an agent’s prompt instead of sending it.
Copy from the command line
Section titled “Copy from the command line”Pipe output to mocante-copy to put it on the clipboard of the device you
are looking from, as pbcopy does on a Mac. It works on a remote host too.
git log -1 --format=%H | mocante-copymocante-copy notes.txtWith file names, it copies the files one after the other. Without them, it copies what comes in on standard input.
mocante puts mocante-copy and mocante-open in ~/.local/bin on each host
when it connects, the folder where Claude Code and other tools put their
commands. Most shells already have that folder on PATH. If mocante-copy
is not found, add ~/.local/bin to your PATH. mocante never replaces a
file there that it did not write, so to use a command of your own with the
same name, put your file there.
- A copy can be up to 768 KB.
- In tmux, the copy goes through tmux’s clipboard. If you set
set-clipboard offin your tmux configuration,mocante-copystops and tells you how to turn it back on. - Over plain HTTP in a browser tab, the browser can refuse the copy. See reach the web UI from another machine.
Pick a renderer
Section titled “Pick a renderer”mocante can draw terminals with one of two engines. Choose in Settings › Terminal › Renderer, or with Terminal renderer: xterm.js and Terminal renderer: Ghostty in the palette.
- xterm.js is the default. It draws text as page elements, which works best with screen readers.
- Ghostty runs Ghostty’s terminal parser and draws to a canvas. Try it if you prefer Ghostty’s behaviour, or if a heavy full-screen program feels slow.
The choice applies to this device only. When you switch, every open terminal reloads and its scrollback starts again from what tmux replays. No work is lost.
Also under Settings › Terminal:
- Terminal theme sets the terminal colours. Follow the app, the
default, gives terminals light colours when the app is light and dark
colours when it is dark. Dark and Light keep one set of colours
whatever the app shows. The palette has the same choices as Terminal
theme: Follow the app, Terminal theme: Dark and Terminal theme:
Light. A program that is already running keeps the colours it chose when
it started. Start it again to make it pick colours for the new background.
Some agents keep a theme of their own that mocante does not change. Claude
Code’s dark theme can be hard to read on a light terminal: run
/themein Claude Code and pick a light theme. - Font size sets the terminal text size. Open terminals change at once and keep their scrollback.
- Option as Meta (macOS only, off by default) makes
Option+key act asAltin terminal programs. Leave it off if you type characters such as@or{withOptionon your keyboard layout.
Adopt a tmux session you started yourself
Section titled “Adopt a tmux session you started yourself”mocante finds tmux sessions on each host that it does not manage yet, and lists them on the Hosts page under Unmanaged sessions found.
- Open the Hosts page from the sidebar header, or pick Adopt session… in the palette.
- Click Adopt… next to the session.
- Under Project, choose a project, or type a name to create one.
- Under Session name, keep the name or type a new one.
- Click Adopt session.
The session keeps running and its programs are not touched. mocante hides tmux’s own status bar in it, because mocante draws the tabs, and turns on mouse support. See also remote hosts.