abnegate/magents

transcripts on disk. **magents** is the shared API over those sessions - an MCP
server plus a small CLI - so one agent can pick up where another left off
without you recapping, ping a *specific live chat* when you are not sitting in
the middle, or start an independent persisted chat for a complete task.
It is not a second copy of history and not a fire-and-forget council. Existing
chats stay the default unit of work; new chats are for independent work that
benefits from its own session and working directory.
Install · Plugins · What you can do · Quick start · Tools · CLI · Releases
Why
You already run more than one coding agent. The pain is not "more models" - it
is **context trapped in another window**.
| Pain | What magents does |
| --- | --- |
| You switched hosts mid-task | Read the live session and continue *here* |
| Agent A hit a wall Agent B owns | Inject into that live chat without you as the messenger |
| A subtask can run alone | Spawn a headless persisted session with a complete prompt + reply path |
What you can do
**1. Handoff without a new thread**
You were in Claude on the disaster-recovery branch. Now you are in Grok. Ask
Grok what they were doing; it reads the live session and continues. No paste
buffer. No "new chat, here's the context."
**2. Send when you are not the messenger**
Three agents running. Claude hits a wall Codex owns. Claude injects into that
Codex thread and keeps going - especially useful when the sender already has the
failing query, file, and constraint you would otherwise reconstruct.
**3. Spawn independent work**
When a task can proceed alone, start a new headless persisted session with a
complete prompt, an isolated working directory when files could collide, and a
request to reply through magents. Spawned agents keep their host's native
approval policy - spawning does not add an approval bypass.
Install
Homebrew (macOS / Linux)
APT (Debian / Ubuntu)
Binary
From Releases:
Assets: magents-x86_64-unknown-linux-musl, magents-aarch64-unknown-linux-musl,
magents-aarch64-apple-darwin, magents-x86_64-apple-darwin.
Container
Cargo
From source
Plugins
Host plugins package the magents skill plus an MCP entry that runs magents mcp.
Install the CLI first (brew install abnegate/tap/magents), then load the matching
folder under plugins/.
| Host | Path |
| --- | --- |
| Claude Code | plugins/claude |
| Codex | plugins/codex |
| Cursor | plugins/cursor |
| Gemini CLI | repo root (gemini-extension.json) |
| AGY CLI / Antigravity | plugins/agy |
Gemini CLI installs the extension straight from this repository:
AGY CLI installs the plugin from plugins/agy (manifest, MCP, and skills):
Details and marketplace notes: plugins/README.md.
Quick start
magents install --all registers the stdio MCP server with each installed host,
skipping hosts whose required binaries are unavailable:
- Grok (grok mcp add magents -- magents mcp)
- Claude Code (claude mcp add --scope user magents -- magents mcp)
- Codex (codex mcp add magents -- magents mcp)
- Cursor (~/.cursor/mcp.json)
- OpenCode ($XDG_CONFIG_HOME/opencode/opencode.json, default ~/.config/opencode)
- Gemini CLI (gemini mcp add -s user magents magents mcp)
- GitHub Copilot CLI (copilot mcp add magents -- magents mcp)
- AGY CLI (agy mcp add magents magents mcp)
It also writes the magents and learn skills under supported hosts' skills
directories (~/.grok/skills/{magents,learn}, ~/.claude/skills/{magents,learn},
~/.cursor/skills/{magents,learn}, and the OpenCode / Gemini / AGY / Copilot
equivalents). /learn reads every local agent's sessions, not only Grok.
For Grok and Codex only, point a host at the binary yourself: