GitWorkStream app icon

GitWorkStream

Catch up on your agents · Mac

See what your agents are doing.

One window that shows what your AI coding agents did across all your projects while you were elsewhere: the new branches, the new commits and the work not yet committed. Catch up at a glance. It only looks, so your work is never at risk.

$8, pay once · macOS 14 or later · Apple silicon · Only looks · No account

GitWorkStream's Timeline: commits across six projects, newest first, with Claude and Codex badges on the ones agents made, and filters for who made them, workstream and repository.

Screenshots taken in private mode, with stand-in names.

The problem

Your agents work in six projects. You can only watch one.

You hand a task to an agent, go to a meeting, and come back to new branches, a dozen commits and half-finished changes spread across your projects. Working out what happened means opening each one in turn and digging through its history.

GitWorkStream puts it all in one window. It works with any agent, any editor and wherever your code is hosted, and because it only looks, it never gets in the way of the work.

While you're away

Step away. Come back to what changed.

GitWorkStream keeps an eye on your project folders. When an agent commits, it appears in the Timeline on its own, labelled with the agent's name and marked NEW since you last looked. It all comes from the files on your Mac, not a server.

The Timeline before: the newest commit is Fold the settings pane at 13:45. The Timeline after: a new commit, Widen stale results by Claude at 15:50, has appeared at the top with a NEW marker.

How it knows

Agents sign their work. It reads the signature.

Most AI coding agents leave clues in the commits they make. GitWorkStream checks three, in order, to tell their work from yours. Nothing to add to your agents: it doesn't read agent logs or anything an agent keeps for itself.

  1. 1A co-author line in the messageCo-authored-by: Claude <…>
  2. 2The author's name or emailname <email>
  3. 3The start of the branch nameclaude/…
ClaudeCodexCopilotCursorAiderDevinand generic bots

The tour

Every view answers one question.

The Timeline: every commit across six repositories with agent badges

Every commit across all your projects, newest first. Filter by workstream or repository, and if you like, show history that was rewritten, such as rebases, resets and amends.

Workstreams

Group what belongs together.

When one piece of work spans several repositories, give it a name and follow it as one. GitWorkStream suggests groups for you, and you decide.

Project · any branch

“These repositories are one product.”

A group of repositories you always look at together, whatever branch each one is on. See what's new and what's not yet committed across all of them at once.

Change set · one shared branch

“This change is one branch in three repos.”

Shows the order to merge them in, which repositories are ready or blocked, the branches not pushed yet, and all the changes together so you can review them in one go.

Optional · Ask About This

Ask your own AI. See exactly what's sent.

Pick a commit or a workstream and ask a question about it, using an AI you already have: Anthropic, OpenAI, a model running on your Mac with Ollama, or another OpenAI-compatible service. No ads, no tracking. Your AI, privacy first.

  • Nothing is sent until you press Ask. The sheet shows the size of what would be sent and exactly where it goes.
  • Local if you like. With Ollama on your Mac, it says “Nothing leaves the machine”, and it doesn't.
  • Kept small. There's a cap on how much code is sent: 60,000 characters unless you change it.
  • Off in private mode. Ask is switched off while stand-in names are on screen.
The Ask sheet for a commit: a private mode notice, What would be sent 553 characters, about 138 tokens, Goes to llama3.1 running on this Mac, Nothing leaves the machine, and suggested questions.

The film

40 seconds. Every cut on the beat.

Safe by design

It only looks. It never touches your work.

It never commits, pushes, pulls, fetches, merges or stages anything. Leave it open while your agents work in the same projects.

  • Never in your agents' way. It reads in a way that doesn't hold git up, so an agent committing at the same moment won't trip over it.
  • No account, no GitHub sign-in. It uses the git already on your Mac. No ads, no tracking. Your AI, privacy first.
  • Careful with code you didn't set up. If a repository's own settings would make git run other programs, GitWorkStream won't read it until you've checked and trusted those exact settings.
  • Your setup is backed up. An automatic backup, plus your last 12 setups, each one a click away with Restore.
~/Library/Application Support/GitWorkStream
$ ls
store.json         # folders, repos, workstreams
store.backup.json  # an automatic backup
snapshots/         # the last 12 setups

# …and inside your repositories?
# nothing. GitWorkStream only reads.

Your code stays yours.

No accountOpen it and point it at a folder.
No ads, no trackingNo analytics, no crash reporting.
Only looksReads git on your Mac. No GitHub sign-in, no agent logs.
Your AI, privacy firstNothing is sent until you press Ask, and you see what goes, and where, first.

Support

Questions, answered.

Something not working, or an idea? Email [email protected] with your macOS version. Replies usually within two working days.

Could GitWorkStream change or break my code?

No. It only looks. It never pushes, pulls, fetches, merges, commits or stages, and it saves nothing inside your projects. It also reads in a way that won't hold up an agent committing at the same time, so it's safe to leave open while agents work. For the curious: it runs git with --no-optional-locks.

How does it know which commits an agent made?

Agents leave clues in the commits they make. It looks for a Co-authored-by line in the commit message first, then the author's name or email, then the start of the branch name, such as claude/. It recognises Claude, Codex, Copilot, Cursor, Aider, Devin and generic bots. It doesn't read agent logs or anything an agent keeps for itself.

Do I need a GitHub account or an API key?

No. There's no account and no sign-in. It reads the projects on your Mac using the git you already have, and never talks to GitHub, GitLab or anywhere else your code is hosted. You'd only need an API key to use Ask About This with an online AI provider.

Does anything leave my Mac?

Only if you set up Ask About This and press Ask. Then the details shown in the sheet go to the AI provider you chose. If you run a model on your Mac with Ollama, nothing leaves the machine. No ads, no tracking: no telemetry, analytics or crash reporting. The privacy policy has the detail.

What is private mode?

A switch in Settings › Advanced that swaps the repository, branch, commit, author and file names on screen for consistent stand-ins, so you can take screenshots or share your screen. A Private label shows in the toolbar, and Ask About This is switched off while it's on. Every screenshot on this page was taken in private mode.

What's the difference between a project and a change set?

A project is a group of repositories you always look at together, whatever branch each one is on. A change set follows one branch across several repositories, and adds the order to merge them in, which are ready or blocked, the branches not pushed yet and all the changes together in one review.

Why won't it read one of my repositories?

That repository's own git settings ask git to run another program, such as a filter or diff tool. GitWorkStream won't read it until you've checked and trusted exactly those settings. This protects you from repositories you didn't set up yourself.

Where is my setup stored?

On your Mac, in ~/Library/Application Support/GitWorkStream/: your folders, repositories and workstreams, a backup, and your last 12 setups, which you can restore from Settings.

Which Macs does it run on, and when is it out?

Macs with Apple silicon running macOS 14 or later. It's coming soon. Email [email protected] and we'll tell you when it's out.