Execution
How AIgency tasks actually run: task kinds, status transitions, and the decision between an isolated git worktree and the shared workspace.
Once a task is assigned, AIgency runs it as a real AgentDock session against either your project's shared working directory or an isolated git worktree, depending on the run's settings.
AgentDock Pro
Task execution is part of AIgency, available only in AgentDock Pro.
Task kinds
standard— ordinary work tasks.integration— always runs directly in the shared workspace, never in an isolated worktree, since its purpose is to bring isolated work back together.verification— checks the result of other tasks.
Task status
A task moves through a status lifecycle with real, distinct meanings:
| Status | Meaning |
|---|---|
pending | Not yet started. |
running | Actively executing. |
waiting_approval | Blocked on a permission decision — see Approvals. |
waiting_interaction | The agent raised a live permission, choice, or auth prompt mid-turn; AIgency pauses the task rather than failing it. |
waiting_capacity | Blocked on provider rate limits or capacity. |
waiting_workspace | Blocked waiting for a workspace slot (for example, an isolated worktree) to become available. |
completed / failed / skipped / stopped | Terminal states. |
Note
The waiting_* states are not failures — time spent in them doesn't count against a task's retry budget, and it doesn't cause dependent tasks to be skipped.
Isolated worktrees vs. the shared workspace
A task runs in its own git worktree only if the run's workspace-mode preference is worktree, or auto combined with a concurrency greater than 1. If the project folder isn't a git repository, or worktree creation fails for any reason, AIgency falls back to running the task directly in the shared workspace rather than blocking the task. Worktrees are created under .aigency-worktrees/<runId>/<taskId> on a dedicated branch per task, with collision-safe slot allocation and automatic cleanup once a task or run is deleted.
Related
- Multi-agent orchestration — how many tasks execute concurrently.
- Git integration → Worktrees — the underlying git mechanics.