Axel, a smiling axolotl in neon colours

Agent orchestration,
designed for Rex.

A year of agent apps taught us what works: threads, and named agents. Axel brings them back to the terminal, on Rex, where your work already lives, on this machine or any other on your tailnet.

Get started curl -fsSL https://axel.md/install | sh

See Axel in action

A quick tour of Axel in Rex. One minute twenty, no audio.

A team of agents.
One terminal.

You stop prompting a generic assistant and start working with specialists, each with its own name, key, skills and budget.

The unit of work is the thread, not the tab. The conversation, every tool call, the diff, the agents that joined. A chat tab dies with its window; a thread doesn’t.

This thread cost$58k tokens, two agents. Every token is counted, per thread and per agent.

Runs the agents you already use. Status comes from hooks or the Agent Client Protocol. No screen scraping.

Claude CodeCodexOpenCodeGooseCursorAny ACP agent

Specialists, not one agent that knows everything. Each named agent carries only its own skills, key, permissions and budget.

Ask, then close the laptop. @terra@mini runs terra on the mini at home. Its branch and uncommitted work come back when you reconnect.

No babysitting. A mode for routine permissions, a guard that still refuses irreversible commands, and a daily budget.

The foundation

Rex fixed the terminal.
Orchestration can live there again.

The agent apps of the past year found the right ideas, then rebuilt the terminal to deliver them: their own windows, their own status lights, their own way to reach a remote machine. Rex, by Superlogical, starts from scratch on what a terminal session is. Axel is just a program in a Rex pane, built on exactly that.

Rex

Why not today?

Two commands. The first time, Axel checks your machine and helps you create your first agent.

$ curl -fsSL https://axel.md/install | sh
$ axel
Read the installation guide