Skip to main content

​
Create a session

Press n in Rakumux mode, click + New session, or press Enter on a folder’s or worktree’s header. Rakumux creates the session straight away with a generated name, selects it and puts you at its shell prompt, with no naming dialog. The session goes in the current folder: the folder of the selected session or header. A single-folder filter takes precedence, and with no folder context the folder you started Rakumux in is used. A session made in a folder the filter hides adds that folder to the filter. For another folder, a program instead of the shell, or startup commands, use the command line:
--detach leaves the session running without attaching to it. See the CLI reference.

​
What a row shows

Each session in the list has three lines:
  1. The name, with the time since it was last active and a status mark on the right. Signed in with AI session titles on, it’s an AI title from what you asked the agent; the ↻ after a hovered name asks for a new one.
  2. The app, running subagents (◈ 3) and what the session reported about itself.
  3. Where it works now, with its git branch (⎇ main, or ⎇ @ and a short commit id when no branch is checked out): see Where each session has worked.
Widen the list by dragging the line beside it to see more of each line.

​
Status marks

The mark on the right of a row says how the session is doing: Rows don’t repeat the status in words; an ended session’s row still says exited · ⏎ restart or dead · ⏎ revive.

​
Rename

Press r in Rakumux mode (Ctrl-\ r from inside the session), or run rakumux rename [<name|id>] <new name>. Sessions you didn’t name can get a better name automatically: signed in, an AI session title from what you asked their agent, or with your own key, AI naming. Automatic names never replace one you chose; asking for a new title (the ↻ after a hovered session’s name, or s) does.

​
Pin

Pinned sessions lead their folder, and lead Ready under the Status tab.
  • With the mouse: point at a session and a star shows just left of its name. ☆ pins it and the gold ★ unpins it, without changing the selection. This needs a terminal that reports pointer movement, as desktop terminals do, over SSH too.
  • With the keyboard: p pins or unpins the selected session, on phones too.
  • From the command line: rakumux pin <name|id> and rakumux unpin <name|id>.
The tab bar and Grid cards show ★ after a pinned session’s name. Every window sees the same pins.

​
Order

The list keeps its order: using a session never moves it, and a new session goes at the bottom of its group, just above + New session. Drag a session up or down (in the Tabs layout, drag its tab left or right), or press J and K, to move it. It stays in its folder (or status, or app), and among the pinned sessions or the others. Your order is saved in ~/.rakumux/config.json.

​
Close, exit and delete

​
Dead sessions and revive

A dead session has no terminal any more, for example after rakumux daemon stop or a reboot. Its saved scrollback is shown dimmed, and Enter revives it: a new terminal in the same folder, its startup commands run again, and an agent picks up where it was.
  • Claude Code, Codex and OpenCode resume the same conversation, with the flags they were started with.
  • Other programs have their last command typed at the prompt, but not run.
After a crash or a reboot the server revives the sessions that were running by itself. See Restarts and recovery.

​
Running Rakumux inside a session

You can run Rakumux inside one of its own sessions, for example over SSH from a session on another machine. That session is marked as the current one and can’t be opened from inside itself.