Skip to content

Git repositories

How AgentDock surfaces git state for the active workspace via the Changes drawer.

AgentDock doesn't provide a full git client. What it does provide, for any workspace that's a git repository, is a Changes drawer: a panel that shows which files have changed and lets you inspect diffs without leaving the conversation.

What the Changes drawer shows

  • A list of changed files for the active workspace's working directory.
  • A diff view per file, so you can review what an agent (or you) changed before deciding what to do next.
  • A revert action for individual files, which discards uncommitted changes to that file.

Requirements

The Changes drawer shells out to a real git executable. AgentDock resolves it from git on your PATH by default; you can point it at a specific binary in Settings → Advanced if git isn't on your PATH or you want to pin a particular install.

Note

If the configured git executable can't be resolved, or the workspace folder isn't a git repository, the Changes drawer has nothing to show.

What it doesn't do

The Changes drawer is a read-and-revert surface, not a git client. It does not stage files, create commits, switch or create branches, merge, or push/pull. For those, use your normal git workflow — a terminal, your IDE, or whatever tooling you already use outside AgentDock. See Commits for more on where that boundary sits.

Reverting a file is a destructive action, and can be gated behind a confirmation prompt — see Safety behaviour.

AgentDock Pro

AgentDock Pro's AIgency orchestration layer manages git branches and worktrees on top of this, scoped to automated task execution. See Worktrees.