Skip to main content
The most common way to use Rakumux is to run several coding agents at once, one per task, and move between them as they need you. This page puts the pieces together.

​
1. One session per task

Start a session for each piece of work and run an agent in it:
1

Start the first agent

In Rakumux mode press n, then run your agent: claude, codex, opencode, or any other.
2

Name it after the task

Press Ctrl-\ to step out, then r to rename the session, for example auth-refactor. Or leave the generated name: with an AI key, Rakumux renames it once the agent settles.
3

Repeat for each task

Each n creates another session in the same folder. Your agents all keep running while you work in one of them.
From a shell or a script, rakumux new --detach --name tests -- claude starts one without switching to it.

​
2. Keep agents apart with worktrees

Agents working on the same repository at the same time are easier to keep apart in separate git worktrees. Rakumux doesn’t create worktrees, but it follows them:
  • Start a session in a worktree’s directory, or let your agent create and move into one.
  • Under the Folders tab, sessions whose agent works in a linked worktree are listed under that worktree’s own header, with its branch, and move as the agent changes worktree.
  • Enter on a worktree’s header starts a new session in it, when the worktree is inside the folder.
The branch beside where each session works comes from the repository’s files, so a switch shows within seconds.

​
3. Triage with the Status tab

Rakumux opens on the Status tab, which groups sessions by what they need from you: Move down the list with j/k, and each session plays live beside it. Signed in, each session is named for what you asked its agent (AI session titles), so you can tell the tasks apart at a glance. Enter goes in, and Esc returns to where you were.
Install the activity hooks so “waiting for you” and “unread” are exact rather than read from the screen.

​
4. Watch several at once

  • Grid (v) shows up to six live terminals as cards, read-only, so you can watch long runs without taking control of any.
  • The App tab groups sessions by agent, useful when you run Claude Code and Codex side by side.
  • Pin (p, or the star next to a name) keeps the sessions you return to most at the top of their folder.
  • The terminal panel (T) gives you a quick shell under the agent you’re watching, for a git diff or a test run, without creating another session.

​
5. Leave them running

Quit with q, close the terminal, or lose your connection: every agent keeps working in the background server. Open Rakumux again, from any terminal, and pick up where you were. After a reboot, the sessions that were running come back by themselves, and Claude Code, Codex and OpenCode resume the same conversation.