Axel CLI
Axel runs named agents on Claude Code, Codex and more in the Rex terminal, and task threads outlive a closed laptop
- 268 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Agents run without confirmations by default, executing commands and editing files, and the guard only refuses irreversible commands
- Each agent holds its own Ed25519 key, and remote machines get a short-lived grant per thread
- The install script runs through curl piped to the shell
Install
- Works in
Manual install
brew install scarce/taps/axelNeeds the Rex terminal and at least one agent harness. Update with `brew upgrade`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Agents run without confirmations by default, executing commands and editing files, and the guard only refuses irreversible commands
- Each agent holds its own Ed25519 key, and remote machines get a short-lived grant per thread
- The install script runs through curl piped to the shell
This is third-party code. Review the repository files before installing.
What it does
Axel is a command-line agent orchestration tool designed for the Rex terminal. Work is built around a thread, an intent and everything done about it. A thread outlives the agent process, the pane and the machine, and every change is recorded as a signed event, so copies on different machines merge. Agents are named. `axel agent new terra codex` creates a worker on Codex, and `axel agent new opus claude/opus` creates a reviewer on another model. Each has its own Ed25519 key, permissions, budget, inbox and skill set. A task starts with `axel thread new --agent terra "add retries to the webhook sender, then ask @opus for a review"`. Axel drives Claude Code and Codex over the Agent Client Protocol with built-in adapters and no Node, and OpenCode, Goose, Cursor, Pi, Devin, Grok Build, Kimi Code, Amp, Hermes Agent and OpenClaw through their ACP modes. Project context and skills live in one `AXEL.md` that `CLAUDE.md` and `AGENTS.md` point to, with versions pinned in `AXEL.lock`. Other machines on the network join with `axel host add mini`, and agent keys never leave the home machine.
Who it is for. Developers who run several vendors' agents on one project and want a builder and a reviewer in one terminal, continuing from any machine.
Good fit when
- One agent writes code while a second on another model reviews the diff, and you need a shared thread with history
- A task runs for hours, the laptop closes and the work should continue and wait for you
- Agents need different permissions and spending limits: wider for the builder, narrower for the reviewer
- Project context and skills should live in one file for every agent
- A home Mac mini on the network should run tasks while the keys stay with you
Not a fit when
- You do not work in Rex: the README lists it as required along with an agent harness
- You need a single agent without a team of builders and reviewers: plain Claude Code or Codex is enough
- You need strict confirmation of every action: by default agents work without asking
- You need proven long-term stability: every `main` build that passes CI ships as a release
Example request
Create agent terra on Codex and agent opus on Claude for reviews and start a thread: add retries to the webhook sender, then a review by opusLimitations
- The Rex terminal and at least one harness are required: Claude Code, Codex, OpenCode, Goose, Cursor or another from the list. The first run checks the machine and helps create an agent.
- By default agents run in autopilot mode without asking. The guard refuses irreversible commands and a budget caps each agent's spend, but a strict mode is a separate setting.
- Updates ship with every `main` commit that passes CI. Keep the version from `brew upgrade` under control.
- Axel works inside a Rex pane, and the README describes no launch outside Rex.
How to disable. Remove the binary with `brew uninstall axel`, or delete it by hand if installed by script. Agents and their keys live in Axel's local store, and thread data can be deleted there. The `AXEL.md` and `AXEL.lock` files in projects delete like ordinary files.
FAQ
How do I install Axel?
Run `brew install scarce/taps/axel` or the install script from axel.md, then run `axel` in a Rex terminal. The first run checks the machine and helps create an agent. A supported harness such as Claude Code is also required.
How does a thread differ from a chat tab?
A thread keeps the intent and everything done about it and outlives the agent process, the pane and the machine. It can resume on another computer because changes are recorded as signed events.
Which agents work through Axel?
Claude Code and Codex are driven by built-in adapters over the Agent Client Protocol. OpenCode, Goose, Cursor, Pi, Devin, Grok Build, Kimi Code, Amp, Hermes Agent and OpenClaw connect through their own ACP modes.
Can agents do irreversible damage?
By default they work without asking, but the guard refuses irreversible commands and a budget caps spend. For strict control give an agent a stricter permission mode.
What is AXEL.md?
One file with project context and a skill list for all agents. `CLAUDE.md` and `AGENTS.md` point to it, and versions of skills from repositories and skills.sh are pinned in `AXEL.lock`.
Discussion
No questions or reviews yet.
Related
CLI toolsECX ties Claude Code and Codex together with shared memory so each sees the other latest messages, plus 19 skills and 21 hooks.
One config for Claude Code and Codex in every repo: shared rules, skill packs, second-model review and a destructive-command guard
One runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass
ReevesAgents runs Claude Code, Codex, Hermes and other CLI agents side by side in tmux; an MCP lets one lead the rest.
A terminal workspace where several CLI agents like Codex, Claude and Gemini exchange messages and work on one task under human oversight
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Axel (this card) | no | 268 | |
| Claude Squad | no | 8,790 | parallel sessions in tmux and git worktrees without signed events or threads shared across machines |
| Conductor | no | 3,791 | a spec-driven development plugin rather than a thread manager with named agents |
README in short
The README opens with an example of two agents and one thread, then lists key features: threads, named agents, Rex's role, supported harnesses, remote machines, a single `AXEL.md` and autopilot guard. Install by curl or Homebrew, Rex requirements and documentation links follow.