Terminal sessions

The Console tab in the Hub is a multi-tab terminal. Each tab is a tmux-backed session running on your VM. Tabs survive page reloads, network drops, and switching between devices.

The tab strip

The tab strip across the top shows one tab per running session. The + New button sits to the right of the tabs, paired with a mode chip that controls what the next new tab launches into. + New is disabled while the page is resolving which session to attach to on initial load.

Modes

Two modes are available:

• Claude (default) — the session boots with claude --dangerously-skip-permissions running. The bootstrap types the command into the tmux pane automatically; Claude is ready the moment the tab opens.
• Bash a plain interactive shell. Run claude yourself if you want it, with or without the skip-permissions flag.

Toggle the mode chip before clicking + New to spawn the next session in the other mode.

Typing

By default every keystroke goes straight to the session, so typing feels slow on far or slow links. Turn on Local Typing in the key bar under the terminal: a box appears where you type a whole message locally and press Enter to send it in one piece (Shift+Enter adds a line). The setting is remembered in your browser.

• Start a message with / and it is typed live in the terminal, so Claude Code's command menu still pops up. After that message, typing is local again.
• Esc, Ctrl-C, Tab and — with an empty box — ↑/↓ reach the session directly.
• Click inside the terminal to type live at any time. Tools like vim need live typing.
• The key bar's Ctrl, Shift and Paste buttons act on the terminal and move focus there; Copy and Scroll to bottom keep you in the box.

Naming tabs

Tabs are renameable. Double-click the tab label to enter rename mode. Type the new name and press Enter to confirm, or Escape to cancel. Renaming also propagates the new label to Claude Code's own session name via /rename so the two stay in sync.

The internal tmux session name (console1, console2, etc.) is auto-generated and separate from the display label. Renaming changes the display label; the underlying tmux session name stays as-is.

Pinning and closing tabs

The tab strip shows the sessions you have pinned. Anything you open — + New, a session picked from the N more dropdown, or a link from elsewhere in the Hub — is pinned automatically, so it stays in your strip across page reloads.

Click the small square on the left edge of a tab to close it. Closing a tab only takes it out of your strip: the tmux session keeps running on the server. If you close the tab you are looking at, the console switches to the next tab, or shows Start a console when none are left.

Pins are stored in your browser, so your strip is yours. Sessions other people opened, and tabs you closed, are listed in the N more dropdown at the end of the strip. Pick one to open it as a tab.

Every pinned tab stays connected in the background, not just the one you're looking at — switching between them is instant, since the tab you switch to is already live and just gets painted on screen.

Terminating

Click the X on the right edge of any tab. A confirmation dialog asks you to confirm before tearing down the tmux session — once terminated, the session and its history are gone for everyone.

Session cap

Each environment caps at 10 concurrent sessions. The + New button becomes disabled when you hit the cap. Terminate a session to create space for a new one.

Surviving reconnects

Tabs are backed by tmux on the VM. If your laptop goes to sleep, your browser refreshes, or the WebSocket drops, the underlying process stays alive on the server. When you come back, the console checks its connection and reconnects by itself, then the tab reattaches to the running tmux session and shows any output that arrived while you were gone.

If the connection to a tab's session dies on its own, the tab shows [Session ended]. Click it to reconnect — no need to close and reopen the tab.