Provider Usage in AIgency
The same canonical provider-usage signal that powers Settings explains why an AIgency task is waiting and when it will automatically recheck.
AgentDock Pro
This page describes how AIgency consumes Provider Usage; the underlying feature is also available outside AIgency — see Provider usage.
AIgency doesn't maintain a separate capacity-tracking system. It reads the same canonical provider-usage/capacity signal that powers the app-wide Provider usage view, so what you see on a waiting_capacity task is consistent with what you'd see checking that agent's usage manually.
Why this matters inside a run
When a task is blocked, its detail view shows the capacity context that put it there — which usually answers "why is this waiting" faster than checking each agent's status individually. This is the same signal capacity recovery's backoff logic acts on to decide when to recheck.