What AgentD is
AgentD runs Claude Code and Codex as a team on your development machine. You plan the work in a chat, workers build it in parallel, and you review every change before you merge it.
AgentD runs on Linux. Releases are published on github.com/libraos/agentd/releases.
What it does
- Connects your agents. AgentD adds an MCP server, hooks and two skills to Claude Code and Codex, so every session shares one task ledger: who is working on what, handoffs, checks and results.
- Gives you a local dashboard.
agentd dashopens Chat, where a planner splits a request into tasks, and Issues, Team and Insights, where you watch each worker and merge its pull request. - Keeps workers on a branch. Each worker runs in its own git worktree with
a budget and a check command, commits on an
agentd/…branch, and never pushes or merges.
Everything runs on your machine. The Console's AgentD page shows the setup steps only: your sessions and tasks are not synchronized to the Console.
AgentD brings no model access of its own. Claude Code and Codex call their models as each is configured: your own sign-in or provider key, or the LibraOS model API. See Models and billing.
Requirements
- Linux with systemd user services. macOS binaries are built but untested.
- git 2.25 or newer, with your name and email set.
- Claude Code or Codex, installed and signed in. One client is enough.
- For Codex workers, bubblewrap (
bwrap).
Install
Download the installer from the latest release, read it, then run it. No GitHub sign-in is needed:
d="$(mktemp -d)"
curl -fsSL -o "$d/install.sh" https://github.com/libraos/agentd/releases/latest/download/install.sh
less "$d/install.sh"
sh "$d/install.sh"
agentd version
The installer checks the release's checksums and installs the binary to
~/.local/bin, with the agentd and agentd-setup skills for Claude Code and
Codex. It changes no client configuration. Add ~/.local/bin to your PATH.
To install a specific version, set AGENTD_VERSION to its tag before running
the installer. All releases are
listed on GitHub.
Next: Connect your coding agents.
Add a Runtime when you need it
Task tracking, handoffs, checks and the dashboard work without the LibraOS Runtime. Knowledge search, copilots and model-written daily reports need a configured Runtime; see Getting started.