Skip to content

Safety behaviour

How AgentDock guards destructive git actions, from file reverts to concurrent worktree allocation.

Git-related safety in AgentDock works at two different levels: a confirmation setting for destructive actions in the Changes drawer, and structural safety built into how AIgency allocates worktrees.

Confirming destructive actions

Reverting a file in the Changes drawer discards uncommitted changes to it — that's destructive. The Settings → Permissions toggle confirmDestructiveGitActions controls whether AgentDock asks you to confirm before doing this. Leaving it enabled means you get a chance to back out before a revert happens.

Worktree allocation safety

AgentDock Pro

When AIgency isolates tasks in git worktrees, it doesn't assume which worktree slots or branch names are free — it checks real git worktree list and git branch output before allocating one, so it won't collide with worktrees that already exist. If a task needs to restart, AIgency reuses or retries its existing worktree rather than creating a conflicting duplicate.

If creating a worktree fails for any reason — the folder isn't a git repository, git errors out, or anything else — AIgency doesn't fail the task outright. It falls back to running the task in the shared workspace instead. See Execution for the full flow.

When multiple isolated tasks' changes need to come back together, AIgency also runs conflict detection between them before integrating, rather than merging blindly.

Related settings