Skip to content

Commits

AgentDock does not stage or commit changes for you — that stays part of your normal git workflow.

AgentDock does not provide an in-app way to stage files or create commits. This is a deliberate scope boundary, not a missing setting: the Changes drawer is a view-and-revert surface, and nothing more.

What this means in practice

  • After an agent makes changes to your workspace, review them in the Changes drawer.
  • If you're happy with them, commit them the way you normally would — a terminal, your IDE's git integration, or any other tool in your workflow.
  • If you're not happy with a specific file's changes, you can revert that file from the Changes drawer instead of committing it. See Safety behaviour for how reverts are guarded.

Warning

Don't expect a "commit" button anywhere in AgentDock's UI — there isn't one. Committing your work is intentionally left to your own git tooling.

AgentDock Pro

The one exception is internal to AIgency: when it isolates a task in its own worktree, it manages that worktree's branch itself as part of orchestrating and later integrating the task's work. That's an internal mechanism for AIgency's own execution, not a general commit workflow exposed to you.