live · scanning local repos
gitpulse — main

GitPulse

All your git repositories in one place — what changed, and where you forgot to commit.

Launch price · −50%Final price €78

€39+ VAT at checkoutLicence agreement

353 licences left at the launch price

Follow GitPulse on X · @gitpulseapp

GitPulse · macOS · menu bar

Scans the folders on your Mac, finds every git repository, and shows you the real state: what is uncommitted, what is unpushed, which branch you are on, what was worked on today. Without opening thirty terminals.

The problem

One repository, you can keep in your head. Thirty, you cannot.

git status tells you about one repository. With thirty, the question is not "what is here" but "where did I leave something behind".

And once you let an automated tool touch git, the question becomes "what can it break" — and usually the answer is "everything".

Step by step

Six steps, in the order they happen. The last two are the agentic part — the rest runs regardless.

01ScanIndexes the folders you point it at and finds every git repository there on its own.
02Show the real stateCurrent branch, modified, staged and untracked files, how many commits you are ahead or behind the remote.
03Track liveUpdates the state as it happens, not only when you open the app.
04Compare against GitHubWith your own token, shows which repositories you never cloned locally and which clones you forgot on disk.
05Propose over MCPClaude Code reads the state through the local MCP server and can propose changes — it never applies them on its own.
06You confirmEvery write needs a confirmation token you give in the app, and lands in the audit log.
// screens

The app's screens

GitPulse finds every repository in the folders you point it at, and the Today dashboard counts what needs a push, a commit or a pull.
Needs Attention sorts what is waiting into five groups, from needs push to branches with no upstream.
With your own GitHub token, GitHub Inventory shows the repositories you never cloned, and the local repositories that have no match on GitHub.
With Allow git actions on and a Pro licence, Claude Code can propose a git action, and your confirm in Agent Review issues a one-time token for that one action.
Force push, reset hard, clean and rebase are blocked in the code, and every call the agent makes is kept in the audit log.
// screen tour

What each screen shows

  1. 01 / 05

    Today: your day, across every repository

    • At the top, the day's counters: active projects, today's commits, how many repositories need a push or a commit and how many are behind their remote, plus modified and staged files.
    • Every project you worked on today gets its own row: current branch, commits, changed files and how far ahead or behind it is, with tags such as Needs Commit or Needs Push.
    • Below them, the repositories with uncommitted changes you did not touch today, so you can see where you forgot to commit.
    • All of it is computed on your Mac, from read-only git commands.
  2. 02 / 05

    Needs Attention: what is waiting on you

    • Five groups: Needs Push, Needs Commit, Behind Remote, Stale Dirty and No Upstream, each with the repository, the branch and how far ahead or behind it is.
    • The number in the sidebar is exactly the number of rows on the page: both come from the same computation.
    • A repository in three groups is listed three times, because there are three things to do.
    • Branches with no upstream have their own group: it is one of the states in which work can be lost.
  3. 03 / 05

    GitHub Inventory: what is on GitHub and what is on disk

    • The list brings together the repositories in your connected GitHub accounts and the local ones, with filters: All, Mapped, Remote Only, Local Only, Private, Stale, Active and Archived.
    • Remote Only shows the repositories you never cloned; Local Only shows the clones with no match on GitHub.
    • A local repository is matched to its GitHub twin by its remote URL.
    • The account connects with your own GitHub token, kept only in the macOS Keychain.
  4. 04 / 05

    Agent Review: the agent proposes, you confirm

    • In Claude Code, the agent asks for a push through the MCP server and gets confirmation_required: it proposes first, then waits for you.
    • The proposal lands in Agent Review with the exact command and the repository it targets. Nothing is applied until you press Confirm.
    • Confirming issues a one-time token, bound to that single action, which expires.
    • The git actions are fetch, pull --ff-only, push and push -u, and nothing else. They are off by default, need a Pro licence, and a push is refused if the repository is behind.
  5. 05 / 05

    MCP: what GitPulse refuses, and what it records

    • The MCP server is local, on a UNIX socket rather than a port. The GitPulseMCP bridge inside the app forwards Claude Code's calls to the running GitPulse.
    • Force push, reset --hard, clean, rebase, merge and checkout -f are refused in code with a dedicated error code, not merely hidden from the interface.
    • The audit log keeps every call the agent makes, with the time and the tool it used.
    • Apart from the confirmed git actions, everything the agent does against git and GitHub is read-only.

In detail

From scan to confirmed proposal

GitPulse scans the folders you point it at, detects git repositories, and shows for each: the current branch, modified, staged and untracked files, how many commits you are ahead or behind, and what was committed today. You get a full dashboard and a summary in the menu bar.

It can connect to GitHub with your own token to compare what you have locally against what exists remotely, telling you which repositories you never cloned and which clones you forgot.

It also ships an MCP server so Claude Code can read that state and propose changes — without being able to apply them. Every write goes through a confirmation you give in the app, with a token that expires. Dangerous git operations — force-push, reset --hard, clean, rebase — are blocked structurally, not merely discouraged.

What it shows

A dashboard for every repository you have

Discovery & local state

04
  • Finds git repositories on its own in the folders you point it at
  • Real state per repository: branch, uncommitted, staged, untracked, ahead/behind
  • A menu-bar summary, without opening the app
  • Tracks changes as they happen rather than by polling

GitHub & sync

01
  • Compares against GitHub with your own token: what you never cloned, what you forgot

AI summaries

01
  • Optional AI summaries: the provider you choose receives repository names, sync state, commit messages and, optionally, a changed-file count — never code, file names or your journal

Safe for automation

03
  • MCP server: Claude Code reads state and proposes, you confirm in the app
  • Dangerous git operations are blocked structurally, not merely discouraged
  • An audit log for every confirmed action

Why you can trust it

Five things the app does exactly as described here.

Online licence, one key per Mac

Writes through MCP (applying mappings, git operations) need an activated licence; rejecting a proposal stays free. Activation contacts me-digital.ro and sends the key, a machine identifier and the Mac's name; it sends nothing about your repositories.

Dangerous git operations are blocked in code

force-push, reset --hard, clean, rebase, merge, checkout -f are refused with a dedicated error code, not merely discouraged from the interface.

Git actions, only if you turn them on

GitPulse is read-only by default. From 3.10, with Settings → Agent (MCP) → "Allow git actions", it can run four actions and only these four: fetch, pull --ff-only, push, and push -u to set an upstream. Each one is proposed first, shows you the exact command and waits for your confirmation in Agent Review. A push is refused if the repository is behind. Needs a Pro licence.

552 automated tests, zero failures

The suite covers binding confirmation tokens to a single action, refusing dangerous commands, and the audit log.

AI summaries never see the code

The feature is off by default. If you turn it on, the AI provider you choose receives repository names and their sync state, commit messages and, optionally, a changed-file count. Your source code, your file names and your journal never leave the Mac. With Ollama, nothing leaves it at all.

What it does not do yet

A dashboard that is honest about its own edges is more trustworthy than one that isn't.

Compares against GitHub only — GitLab and Bitbucket are not covered.
Does not sync state across Macs — everything is local, per machine.
The GitHub token is added by hand — there is no OAuth flow.

Requirements

System
macOS 14.0 or later
Architecture
Universal binary — Apple Silicon and Intel
Signing
Developer ID, notarised by Apple — Gatekeeper accepts it with no warning
Network
GitHub REST API (optional), the licence (me-digital.ro), updates on request and, if you enable summaries, the AI provider you chose

Questions

A single payment, no subscription. The launch price, the final price and how many licences are left at the launch price are shown at the top of this page.

Not through dangerous commands: force-push, reset --hard, clean, rebase, merge and checkout -f are blocked by the app. Every other write needs a confirmation token you give yourself, in the app.

Yes. The build you download is signed with a Developer ID (Team 83S677R8NP) and notarised by Apple — spctl marks it "accepted", and an ordinary double-click is enough on first launch.

Repository names and their sync state, commit messages and, optionally, a count of changed files. Never the source code, your file names or your journal. The feature is off by default.

Not yet — the remote comparison is built for GitHub only.

Purchase

GitPulse for Mac

Built with

SwiftSwiftUIGitGitHubMCP
Launch price · −50%Final price €78
€39

+ VAT, calculated at checkout for your country

353 licences left at the launch price

Licence agreement

Activation

How to activate your licence

Download the app

Download version 3.10.1

7.6 MB

Open the app, choose Actions → Activate Licence… (or click “Activate licence” in the bar at the bottom), paste the key from the email and press Activate.

On X

What GitPulse has posted on X. Each post opens on X.