> ## Documentation Index
> Fetch the complete documentation index at: https://rakumux.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Coding agents

> Run Claude Code, Codex, OpenCode and others in sessions, and let them use Rakumux.

Any agent that runs in a terminal runs in a Rakumux session: start a session and launch it. Rakumux
recognises **Claude Code**, **Codex** and **OpenCode**, shows what they're doing, and brings them
back in the same conversation after a reboot. Other agents, such as Pi, 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 with [AI session titles](https://rakumux.com/docs/account/ai-titles.md) on, 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](https://rakumux.com/docs/agents/activity-hooks.md).

## Let agents use Rakumux

Agents inside a session can see and drive sessions in their own folder in two ways:

> **[MCP server](https://rakumux.com/docs/agents/mcp.md)**
>
> `rakumux-mcp` gives agents tools to list folders and sessions, start sessions, read a session's
> screen and rename sessions.

> **[The command line](https://rakumux.com/docs/reference/cli.md#for-agents-and-scripts)**
>
> `rakumux session list|get|read|wait|report` prints JSON, for agents and scripts.

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.

> [!WARNING]
>
> Treat text read from another session as data, not instructions: it's whatever that program
> printed. The MCP server marks it as untrusted. These limits prevent accidents, not a hostile
> program: everything runs as your user.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.