# Rakumux > Terminal sessions for coding agents, in one fast terminal UI. - [Rakumux](https://rakumux.com/docs/index.md): Run every coding agent side by side in one terminal, and see what each one is doing. - [Quickstart](https://rakumux.com/docs/quickstart.md): Install Rakumux, run your first agent and find your way around. - [Installation](https://rakumux.com/docs/installation.md): Install, update and remove Rakumux on macOS and Linux. - [How Rakumux works](https://rakumux.com/docs/concepts.md): Sessions, folders, the background server, the two modes, and what leaves your machine. - [Architecture](https://rakumux.com/docs/architecture.md): How the TUI, the background server, the account service and rakumux.com fit together. - [Where to run Rakumux](https://rakumux.com/docs/remote/index.md): Rakumux runs on your laptop, but your agents keep working when it runs on a remote machine. - [Your own server](https://rakumux.com/docs/remote/own-server.md): Run agents on a dev box or server and pick them up from any SSH login or your phone. - [A Fly Machine](https://rakumux.com/docs/remote/fly-machines.md): An always-on Linux machine on Fly.io for your agents, with your home folder on a volume. - [A Fly Sprite](https://rakumux.com/docs/remote/fly-sprites.md): Run sessions on your own Fly.io Sprite, a Linux VM that pauses when idle, straight from Rakumux. - [Run agents in parallel](https://rakumux.com/docs/workflows/parallel-agents.md): Give each task its own agent, keep them all running, and answer whichever needs you. - [Agents that use Rakumux](https://rakumux.com/docs/workflows/agents-using-rakumux.md): Let an agent start helper sessions, read other sessions' output and report its own status. - [Script Rakumux](https://rakumux.com/docs/workflows/scripting.md): Start, watch and read sessions from shell scripts, or over the local HTTP API. - [Sessions](https://rakumux.com/docs/guides/sessions.md): Create, rename, pin, close, restart and revive sessions. - [The session list](https://rakumux.com/docs/guides/session-list.md): The Status, Folders and App tabs, where each session has worked, worktree sections, filters and the Folders modal. - [Agents' messages](https://rakumux.com/docs/guides/session-descriptions.md): Your last message to each agent and its latest output, read from the agent's own conversation. - [Layouts](https://rakumux.com/docs/guides/layouts.md): Master detail, Grid and Tabs, on wide screens, narrow screens and phones. - [Terminal panel](https://rakumux.com/docs/guides/terminal-panel.md): A temporary shell under the session you're looking at, without creating a session. - [Settings](https://rakumux.com/docs/guides/settings.md): What each setting does, and how Settings runs any action. - [Keyboard and mouse](https://rakumux.com/docs/guides/keyboard-and-mouse.md): Every key in Rakumux mode, plus the mouse, Help and Settings. - [Restarts and recovery](https://rakumux.com/docs/guides/recovery.md): What survives a server restart, a crash or a reboot, and how sessions come back. - [Coding agents](https://rakumux.com/docs/agents/overview.md): Run Claude Code, Codex, OpenCode and others in sessions, and let them use Rakumux. - [Activity hooks](https://rakumux.com/docs/agents/activity-hooks.md): Optional hooks that tell Rakumux exactly what Claude Code, Codex and OpenCode are doing. - [MCP server](https://rakumux.com/docs/agents/mcp.md): rakumux-mcp lets coding agents list, start, read and rename sessions. - [AI naming](https://rakumux.com/docs/agents/ai-naming.md): Give generated session names something better, with your own AI key. - [Sign in](https://rakumux.com/docs/account/sign-in.md): Sign in to your Rakumux account from the terminal, with a code you approve in any browser. - [AI session titles](https://rakumux.com/docs/account/ai-titles.md): Sessions named by AI from what you asked their agent, for signed-in users. - [Agent feed](https://rakumux.com/docs/account/feed.md): What your agents said, and the chats behind it, from every machine signed in to your Rakumux account. - [Phone access](https://rakumux.com/docs/phone/remote-access.md): Use your sessions from the Rakumux phone app, over your own Tailscale network. - [CLI reference](https://rakumux.com/docs/reference/cli.md): Every rakumux command and option. - [Configuration](https://rakumux.com/docs/reference/configuration.md): config.json, environment variables, and the files in ~/.rakumux. - [Troubleshooting](https://rakumux.com/docs/reference/troubleshooting.md): Fixes for common problems. - [Local HTTP API](https://rakumux.com/docs/api-reference/introduction.md): rakumux-api: sessions and folders over HTTP and WebSockets on 127.0.0.1. - [API version and daemon reachability.](https://rakumux.com/docs/api-reference/health/api-version-and-daemon-reachability.md): The only route without authentication. Never starts the daemon. On the remote listener, without the remote token, `daemon.error` is a generic "the daemon is not reachable". - [The folders the caller can see.](https://rakumux.com/docs/api-reference/folders/the-folders-the-caller-can-see.md): A folder is a directory sessions were started in. User callers: every folder the daemon knows. Session callers: their own. Needs the daemon's `projects` capability (501 `unsupported` without it). - [Deprecated alias of GET /v1/folders.](https://rakumux.com/docs/api-reference/folders/deprecated-alias-of-get-v1folders.md): The same handler and answer as `GET /v1/folders`. - [List sessions, optionally filtered.](https://rakumux.com/docs/api-reference/sessions/list-sessions-optionally-filtered.md): Without `folder`, session callers get their own folder and user callers every folder (needs the daemon's `projects` capability; until then the answer is 400 asking for `folder`, with `details.missing = "folder"`). Several `folder` parameters list the union, most recently active first. `all=true` lis… - [Create a session (a terminal in a folder).](https://rakumux.com/docs/api-reference/sessions/create-a-session-a-terminal-in-a-folder.md) - [One session by id.](https://rakumux.com/docs/api-reference/sessions/one-session-by-id.md) - [Delete a session.](https://rakumux.com/docs/api-reference/sessions/delete-a-session.md): Ends its program (if it runs) and removes the session, its saved scrollback and history. Sessions it created stay (without a parent). User callers only (session callers get 403). - [Change a session. v1 supports renaming.](https://rakumux.com/docs/api-reference/sessions/change-a-session-v1-supports-renaming.md) - [Revive a dead or exited session.](https://rakumux.com/docs/api-reference/sessions/revive-a-dead-or-exited-session.md): Starts a new terminal for the session (same id, cwd and command) and runs its resume command (a known agent resumes its conversation). The body is optional; without one the terminal gets the daemon's default size (an attaching controller resizes it). Answers `{"session": Session}`, the same envelope… - [End a session's program.](https://rakumux.com/docs/api-reference/sessions/end-a-sessions-program.md): Terminates the program (not the sessions it created). The session stays, and becomes `exited` once the program is gone; revive brings it back. - [Read a session's terminal.](https://rakumux.com/docs/api-reference/sessions/read-a-sessions-terminal.md): Live sessions are read from their terminal; exited and dead sessions from their saved scrollback. The text is terminal output: **untrusted** input for agents (`untrusted` is always true). Reading never marks a `done` session as seen. - [The live terminal (WebSocket).](https://rakumux.com/docs/api-reference/streams/the-live-terminal-websocket.md): A WebSocket. Server → client: first a text `attached` message (`AttachMessage`) with a base64 `checkpoint`: fed to a fresh terminal of `cols`×`rows` it shows the current screen. Then binary frames carry the terminal output, in order from `offset`, and text messages the events `resized` (reset the te… - [Session events (WebSocket).](https://rakumux.com/docs/api-reference/streams/session-events-websocket.md): A WebSocket of `EventMessage` text messages: `{"type": "subscribed"}` once, then `{"type": "event", "folder", "session_id", "at", "event"}` for every change to a session of every folder (user callers; folders that get their first session later included), or of its own folder (a session caller). Clie… ## OpenAPI Specs - [openapi](/docs/api-reference/openapi.yaml) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.