Skip to content

Git overview

A built-in git client for staging, committing, branching, merging, and viewing history.

Available on
  • Desktop
  • Web Portal
  • Mobile

Glueprint ships a full git client so you don’t have to leave the app to commit, branch, or resolve a merge. It uses your system git binary under the hood — the same repo state you’d see from any other git tool.

Where to find it

Open the Worktree view from the desktop nav rail. The view has two sub-tabs:

  • Changes — the staging / commit flow, with the commit bar at the bottom.
  • History — the commit graph and per-commit actions.

A header row above the tabs shows the active worktree and branch, sync status, and an Actions menu for everything that doesn’t live in the main flow (compare worktrees, stash, merge, rebase, pull, fetch, remove worktree, refresh).

The portal mirrors the desktop — same Changes / History tabs, same conflict resolver, same stash and merge menus. The mobile app has a slimmer view focused on changes and committing.

How it stays current

A file watcher monitors every active working directory and refreshes git state whenever the disk changes — agent edits, your own edits, externally-applied patches all show up automatically. You don’t need to refresh manually.

When several sessions share a working directory, Glueprint dedupes the watcher so only one git subprocess runs per directory, fanned out to every session that needs it.

Live indicators outside the Worktree view

You’ll see git activity surfaced elsewhere too:

  • Sessions sidebar — each session shows live +N -N counts for unstaged changes in its working directory.
  • Nav rail Worktree icon — shows a badge with the number of worktrees that have changes or unpushed commits.
  • Dashboard git row — sorts worktrees by urgency, splits per working directory, capped at five.

What it does

  • Stage and unstage by file or by hunk; discard with confirmation.
  • Inline diffs and a side-by-side diff overlay.
  • Branch create, switch, rename, delete; pull, fetch, sync, publish.
  • Tags from the commit row in History, or a dedicated Create Tag dialog.
  • Stash with optional include-untracked; apply, pop, drop.
  • Merge and rebase with a VS-Code-style 3-pane conflict resolver.
  • History view with a commit graph (lanes), full search, and per-commit actions (checkout, cherry-pick, revert, reset, tag).
  • Side-by-side worktree compare for diffing two worktrees against each other.
  • GitHub Pull Request creation via the gh CLI.

What it depends on

  • git must be installed and on your PATH. Glueprint shells out to it for every operation.
  • gh (GitHub CLI) is required for Pull Request creation only. If gh isn’t installed or signed in, the Create PR modal explains the issue. Everything else works without gh.

There are no Glueprint-specific git settings — your existing .gitconfig, hooks, and credentials apply unchanged.

PreviousThe built-in MCP server
NextWorktrees and compare