Manual Git Actions
- Desktop app
- All plans
What it does
The Changes tab runs git for you from four buttons, on the branch it already shows: Fetch, Pull, Merge and Push. No agent and no terminal are involved. Each button runs the command behind the scenes and says how it went: a success message that disappears on its own, or git's complete error message, which stays until you close it.
Where to find it
Right panel > Changes tab, on the row of the branch name: the four icons, in that order. They act on the checkout the tab is reading: the project, or the worktree picked in the Worktree selector.
How to use it
- Fetch: reads the remote without changing your files, then says how many commits there are to pull.
- Pull: brings the remote commits into your branch, with your Pull method (see Git Pull Method). It is off when there is nothing to pull.
- Merge: lists your local and remote branches, with a search field when the list is long. Pick one and confirm: it is merged into the current branch. A remote branch such as
origin/mainis listed even when a localmainexists, so you can Fetch, then merge what you just fetched. - Push: sends your commits. It is off when there is nothing to push.
A merge commit waits to be pushed like any other commit: the Push count goes up after a Merge.
If the merge hits a conflict, it is cancelled: your files stay as they were, and the message lists the conflicting files. If the branch you merged has its own worktree with uncommitted files, a message says those files were not merged and stays until you close it.
Settings
None for the buttons themselves. Their row can be hidden in Settings > Interface > Fetch, pull, merge, push (see Interface Elements). Pull follows gitPullStrategy (see Git Pull Method).
Agent tools (MCP)
None. These buttons are for you; an agent runs git in its own terminal.
Providers
All providers, no difference. It is plain git, not an agent feature.
Mobile
The mobile companion has Commit and Push in its Changes screen, not Fetch, Pull or Merge.
Limits
Works the same on macOS, Windows and Linux, and on a project opened on a server. There is no conflict editor: to resolve a conflict, run the merge in a terminal or in your Git client, or ask an agent. A merge needs a current branch: the button is off on a detached HEAD. git refuses a merge when uncommitted files would be overwritten, and it refuses one while another merge is unfinished: in both cases the message says so and nothing changes.
Common questions
- Can I run git without an agent or a terminal? Yes: Fetch, Pull, Merge and Push are buttons in the Changes tab, next to the branch name.
- How do I merge a branch into the current one? Changes tab > the Merge icon between Pull and Push, then pick the branch and confirm.
- How do I update my branch from
origin/main? Fetch, then Merge and pickorigin/main. - How do I know a fetch worked? A message says how many commits there are to pull. If it fails, git's error stays on screen until you close it.
- What happens on a merge conflict? The merge is cancelled, nothing changes, and the message lists the conflicting files. Resolve it in a terminal or in your Git client, or ask an agent.
Related
- Git Pull Method: how Pull brings the remote commits in.
- Git Worktrees: merging a worktree's branch from the worktrees overview, or automatically when its ticket closes.
- External Git Client: opening the repository in your own Git client.
- Per-Agent Review: the rest of the Changes tab.