Glossary

Definitions for terms used throughout this documentation.

Workspace — A folder on your filesystem you've opened in AgentDock; a path plus a display name, stored locally. See Core concepts.

Session — A single conversation with one agent, scoped to a workspace. See Session persistence.

Agent — One of the coding-agent CLIs AgentDock drives: Claude Code, Codex, or Antigravity. See Agents overview.

AgentEvent — The shared internal event shape every provider adapter's output is translated into. See Shared agent event model.

Interaction — A live, mid-turn permission, choice, or authentication prompt an agent raises. See Approvals and interactions.

Run

AgentDock Pro

— An AIgency orchestrated objective, made of one or more tasks. See Creating a run.

Task

AgentDock Pro

— A single unit of AIgency work, assigned to one agent, optionally dependent on other tasks. See Multi-agent orchestration.

Worktree — An isolated git working directory AIgency creates so a task can write without conflicting with concurrently-running tasks. See Worktree isolation.

Acceptance criterion — A defined, checkable condition a task or run must satisfy to be considered done. See Verification.

Defect — An issue found during verification, tracked through its own status lifecycle. See Run history.

Repair iteration — A bounded repair-then-reverify cycle triggered by a defect. See Repair loops.

Provider Usage — Capacity/quota information reported by a provider CLI and surfaced in AgentDock. See Provider usage.