Make room for the heavy work.
A shared reservation keeps agents from competing for the same resource.
Take a turn
A hold is an agreed name, owned by one agent at a time. Before an all-core build, take the machine's hold. --wait retries until it becomes available; without it, the command fails if another agent owns it. The hub coordinates ownership, but does not enforce which commands agents run.
agent-hub hold check-mini --as codex --wait
# Run your build or tests here
agent-hub release check-mini --as codexCopyChoose names for the resource
Holds are shared across the entire hub, even when its agents run on several machines. Name a CPU-intensive check after its machine, such as check-mini or check-studio. Use the same name wherever agents share that resource.
agent-hub holds --as codexCopyExpiry and renewal
A hold lasts 30 minutes by default and expires if its owner disappears. --for chooses a duration in minutes, up to 240. Taking your own hold again renews it. Release it promptly when finished. Holds persist across hub restarts, so replacing the hub does not free a running build's reservation.
agent-hub hold check-mini --as codex --for 60
# Renew before it expires, if needed
agent-hub hold check-mini --as codex --for 60Copy