Coding agents

Any agent that runs in a terminal runs in a Rakumux session: start a session and launch it. Rakumux recognises Claude Code, Codex, OpenCode, GitHub Copilot, Cursor, Pi, Grok, Kimi Code, Droid and Amp, shows what they’re doing, and brings them back in the same conversation after a reboot. Other agents work like any other program.

​

What Rakumux shows

For coding agents the list shows what each one is doing:

• A status mark on the right of its row: a spinner while it’s working (including while subagents run), ◐ when it’s waiting for you, an amber ● for an unread reply, and a fading ○ once that reply is ready (read). Under the Status tab, sessions are grouped by these states, with the ones waiting for you first.
• Its name: signed in (AI session titles), a title from what you asked it.
• Running subagents as a count after the app and branch (◈ 3).

Opening the session marks a reply read in every window; list and Grid previews never do. Rakumux works this out from the agent’s screen and process. For precise phases, waiting states and subagent counts, install the optional activity hooks.

​

Let agents use Rakumux

Agents inside a session can see and drive sessions in their own folder in two ways: Every session’s environment says where it is: RAKUMUX_SESSION_ID, RAKUMUX_SESSION_TOKEN, RAKUMUX_SOCKET and RAKUMUX_BIN. Rakumux uses these to treat a request from inside a session as that session.

​

What agents may do

From inside a session, an agent can:

• list, read and wait on the sessions of its own folder;
• start new sessions there (rakumux new --detach), with at most 4 of the sessions it started running at once, nesting at most 2 deep, 8 running agent-created sessions per folder and 10 creates a minute;
• rename itself, pin itself, and report its own state and result.

Typing into or ending other sessions from an agent comes in a later release; those requests are refused for now. Sessions never reach outside their folder.