The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the AgentPool listing page.
You pay for several coding-agent subscriptions — Codex, Claude Code, Cursor, Copilot, Devin, Droid — but you work in one at a time. The rest sit idle until your active provider hits its 5-hour or weekly limit, and then you stall.
AgentPool is a local Python CLI and MCP server that reads the live usage limits of every coding-agent subscription you have and lets you — or your primary agent — offload work to whichever one still has headroom. Use the capacity you already pay for, and keep moving instead of hard-stopping at a cap.
It is a control plane, not an auto-router. AgentPool exposes live provider, model, session, artifact, lease, and best-effort usage/capacity state, and runs the work you offload as explicit worker sessions. You or your agent still choose the provider and model — AgentPool makes the limits visible so that choice is informed, never automatic.
The v0.1 alpha posture is conservative:
provider=auto is rejected.PATH.termctrl on PATH for the Terminal Control runtime.AgentPool publishes to PyPI as agentpool-cli; the installed command is
agentpool.
Then:
The agentpool-cli package installs on macOS, Linux, and Windows, but live
terminal runtimes are supported on macOS or Linux (Windows via WSL).
Optional Terminal Control config:
Install from source:
Or run from a development checkout:
A GitHub release install (wheel pinned to a tag, no PyPI required) is also supported:
See docs/install.md for first-run, upgrade, and MCP setup notes.
For AI agents, start by loading the bundled version-matched skill:
That last command is the one you will run most: it shows every configured
subscription's remaining limit, reset time, and a usable flag, so you can see
at a glance which provider to offload the next task to.
Start an explicitly selected read-only worker:
spawn defaults --initial-prompt-mode to provider_default. For Codex CLI
this resolves to arg, which passes the first task as the Codex prompt argument
instead of relying on a paste-and-submit startup cycle. Providers that expose
reasoning controls also accept process-local overrides such as
--reasoning-effort high; Codex also accepts --service-tier priority.
AgentPool does not edit your provider config.
For AgentPool-created edit isolation, choose worktrees explicitly:
Worktree isolation is not forced by default. Users often have their own
worktree setup and cleanup rules, so AgentPool only creates a worktree when
requested through --isolation worktree or policy configuration.
usage-summary returns a providers object keyed by provider id. It is not
ordered and it is not a recommendation list. Each row includes usable,
unusable_reason, quota windows, confidence, age/staleness, and reset timing when
the provider exposes it. The older CLI capacity-summary command is retained
as a human convenience alias; MCP also exposes get_capacity_summary as a
compatibility alias for get_usage_summary.
The default buffer is policy.min_remaining_percent = 10. If any reported
quota window is below that buffer, the provider row is marked unusable for the
summary. Staleness is reported as age information only; it does not by itself
make a provider unusable. If you want cached summary reads to refresh
automatically after a threshold, set policy.usage_auto_refresh_after_seconds
in ~/.agentpool/config.yaml.
AgentPool still does not pick an alternative provider for you.
MCP usage refreshes are intentionally bounded and may return partial=true;
use the CLI commands above when a shell-capable agent needs a complete live
refresh. Use --no-interactive or AGENTPOOL_NO_INTERACTIVE_USAGE=1 when a
shell script must avoid provider TUI fallback probes.
| Provider id | Command | Usage status in v0.1 | Model pinning |
|---|---|---|---|
codex-cli | codex | native local app-server rate-limit probe; CodexBar optional | --model + config-scoped reasoning/service tier |
cursor-cli | agent or cursor-agent | optional CodexBar Cursor usage; native CLI usage is interactive /usage only | --model + read-only --mode ask |
claude-code | claude | temporary /usage probe; ccusage telemetry optional | --model + --effort |
devin-cli | devin | Devin/Windsurf plan-status API from existing CLI auth, with /usage fallback | --model |
copilot-cli | gh copilot | GitHub Copilot usage API from env or gh auth token | forwarded --model |
droid-cli | droid | unknown unless surfaced by future safe probe | process-local settings file + --reasoning-effort |
opencode | opencode | configured adapter; usage unknown in this alpha | --model with provider/model ids |
Compatibility note: the PRD calls Factory's coding product factory-droid, but
AgentPool exposes it as droid-cli because the installed command is droid.
Do not add a duplicate factory-droid inventory row unless a distinct harness
appears.
AgentPool is local-first, but usage probes can still be sensitive because they read existing CLI auth state and may call provider APIs on explicit refresh.
AgentPool does not:
AgentPool does store:
~/.agentpool/artifacts by default;Run:
See SECURITY.md and docs/usage-detection.md.
Start the MCP server:
Example host config:
Verified install helpers (deeplink or one-liner shell command):
Raw config generators:
Use --absolute-command if the MCP host does not inherit your shell PATH.
Verified per-host steps live in docs/mcp-clients.md.
Team templates: .cursor/mcp.json.example,
.mcp.json.example, and docs/examples/README.md.
MCP Registry metadata: server.json. It advertises the
agentpool-cli PyPI package and should be bumped with each release. Release
checklist: docs/release.md.
Provider setup guides:
Cursor,
Cursor Agent CLI,
Codex,
Claude Code,
Copilot,
Droid, and
Devin.
MCP-connected agents should read these once on connect:
agentpool://onboardingagentpool://skill.mdagentpool://preferences.mdThen use tools for live operations. The user-owned preferences file also shows
up through agentpool preferences and get_delegation_preferences(). It may
say to use your native subagent system instead of AgentPool for some tasks. The
default MCP toolset is deliberately small: inventory, usage snapshot, usage
summary, provider models, preferences, spawn, observe, poll, send, interrupt,
collect, artifact manifest, transcript paging, and terminate. Add opt-in
toolsets with agentpool mcp --toolsets default,stats,sessions,leases,worktrees.
Shell-capable agents can use agentpool skills get agentpool instead of MCP
resources to load the same core usage guidance from the installed CLI.
Coding agents with shell access should prefer the CLI path. It is more
token-efficient because large worker output stays in artifact files and
observe/collect return compact manifests by default. MCP remains first-class
for MCP-native hosts and no-shell environments. See
docs/agent-cli-and-mcp.md.
Development and CI checks are documented in CONTRIBUTING.md.