GitWorkStream app icon

GitWorkStream

Read-only git window · Mac

See what your agents are doing.

A read-only window onto every repository you work in. The branches being created, the commits being made and what's still uncommitted, including the work AI coding agents do while you're elsewhere.

macOS 14 or later · Apple silicon · Reads git, nothing else · No account

GitWorkStream's Timeline: commits across six repositories, newest first, with Claude and Codex badges on the commits agents made, and filters for Made by, workstream and repository.

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

The problem

Your agents work in six repos. You look at 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 checkouts. Finding out what happened means a terminal per repository and a lot of git log.

GitWorkStream puts it all in one window. It reads git and nothing else, so it works with any agent, any editor and any host, and it never gets in the way of the work.

While you're away

Step away. Come back to what changed.

Your folders are watched, so a commit an agent makes shows up in the Timeline on its own, badged with the agent and marked NEW since your last look. It works 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

Read from git. Nothing else.

Agents leave traces in the commits themselves. GitWorkStream checks three, in order. It doesn't read agent logs or any agent's own data.

  1. 1A Co-authored-by trailerCo-authored-by: Claude <…>
  2. 2The author's name or emailname <email>
  3. 3The branch prefixclaude/…
ClaudeCodexCopilotCursorAiderDevinand generic bots

The tour

Every view answers one question.

The Timeline: every commit across six repositories with agent badges

Every commit across every repository, newest first. Filter by workstream or repository, and show rebases, resets and amends read from the reflog.

Workstreams

Group what belongs together.

When one piece of work spans several repositories, give it a name. GitWorkStream proposes groupings for you, and you decide.

Project · any branch

“These repositories are one product.”

A standing group of repositories, whatever branch each one is on. See what's new and what's uncommitted across all of them at once.

Change set · one shared branch

“This change is one branch in three repos.”

Adds a landing order, a ready or blocked state per repository, the branches not pushed yet, and a combined diff you can review in one pass.

Optional · Ask About This

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

Select a commit or a workstream and ask a question about it, using the model you already have: Anthropic, OpenAI, Ollama running on your Mac, or any OpenAI-compatible endpoint.

  • 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.
  • Capped. The diff sent is limited in size, 60,000 characters by default.
  • Off in private mode. Ask is blocked 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.

Read-only by design

It reads git. It never writes.

No push, pull, fetch, merge, commit or stage. Safe to leave open while agents work in the same checkouts.

  • No lock fights. Git runs with --no-optional-locks and never fetches, so reading doesn't get in the way of an agent committing.
  • No account, no GitHub, no API. It uses the git already on your Mac. Without Ask set up, it makes no network connections at all.
  • Careful with strangers' repos. If a repository's own config would run programs, GitWorkStream won't run git there until you trust those exact settings.
  • Hard to lose. An automatic backup, and the last 12 snapshots of your setup with a Restore button.
~/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 telemetryNo analytics, no crash reporting, no tracking.
Reads git onlyNo GitHub, no API, no agent logs.
You press AskThe optional AI sheet shows 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.

Can GitWorkStream change my repositories?

No. It never pushes, pulls, fetches, merges, commits or stages, and it stores nothing inside your repositories. It runs git with --no-optional-locks, so it doesn't take the optional locks that could trip up an agent committing at the same time. Safe to leave open while agents work.

How does it know which commits an agent made?

From git alone. It looks for a Co-authored-by trailer first, then the author's name or email, then the branch prefix, such as claude/. It recognises Claude, Codex, Copilot, Cursor, Aider, Devin and generic bots. It doesn't read agent logs or any agent's own data.

Do I need a GitHub account or an API key?

No. There's no account and no sign-in. It reads the repositories on your Mac with the git already installed, and never talks to GitHub, GitLab or any other git host. An API key is only needed if you choose to use Ask About This with a hosted model.

Does anything leave my Mac?

Not unless you set up Ask About This and press Ask. Then the commit or workstream details shown in the sheet go to the provider you chose. With Ollama on your Mac, nothing leaves the machine. There's no telemetry, analytics or crash reporting. The privacy policy has the detail.

What is private mode?

A switch in Settings › Advanced that swaps repository, branch, commit, author and path names on screen for stable stand-ins, so you can take screenshots or share your screen. A Private marker shows in the toolbar, and Ask About This is blocked 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 standing group of repositories, whatever branch each one is on. A change set follows one shared branch across repositories, and adds a landing order, a ready or blocked state per repository, unpushed branches and a combined diff you can review in one pass.

Why won't it read one of my repositories?

That repository's own git settings name a program for git to run, such as a filter or diff driver. GitWorkStream won't run git there until you trust exactly those settings. This protects you from repositories you didn't set up yourself.

Where is my setup stored?

In ~/Library/Application Support/GitWorkStream/ on your Mac: your root folders, repositories and workstreams, a backup, and the last 12 snapshots of your setup, 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.