Vibe code from one app.
Run your agents side by side in their own worktrees, read what they wrote in a UI made for reviewing, test it and commit. Without an editor eating gigabytes of RAM.
brew install --cask emircan-sahin/tap/gitviberGitViber with three agents, each in its own worktree. The open worktree's diff fills in line by line as the agent saves.
01One window
One window. Not four.
No editor to read the files, no GitHub Desktop for the diffs, no pile of terminals.
02Worktrees
Many agents. One screen.
Give every agent its own worktree. They work side by side without stepping on each other, and you switch between them from the top bar.
03Live diffs
Watch the work land.
The diff refreshes the moment an agent saves, without losing your place. No reloading, no git status.
04Switching
Hop between them.
Each worktree keeps its own terminals and its own review progress, so nothing gets lost when you switch.
05Any starting point
Start from anything.
Any branch or commit, or check a pull request out into its own worktree without touching yours.
06Review
Built for reading code, not typing it.
Agents turned the day into reading code. Walk the changed files with the keyboard, mark them viewed, and when an agent touches one again, the mark clears so you know to look again.
07Terminal
Test it without leaving the diff.
A real terminal sits under the diff, with tabs and splits. Run the tests, start the dev server or talk to the agent, right next to the change you're reading. ⌘J toggles it.
08Explorer
Browse the code, not just the diff.
A full file explorer with change bars in the gutter, and ⌘P to jump to any file. Fix a line right in the file view and save it. For most days, that's the editor you no longer need open.
09Commit
Your agent writes the message.
Hit the sparkle next to the commit box and your own claude -p or codex exec writes it from the diff. No API key, no extra account.
Not another editor eating your RAM.
Editors like Cursor easily take gigabytes just to let you read.
~14 MB
The whole app.
GitHub Desktop is 681 MB. GitViber has no bundled Chromium: a Rust core and the system webview.
0%
CPU at idle.
It wakes up when files change, not on a timer. Diffs are computed in Rust and highlighted off the main thread.
And the rest of git.
Your own git 2.36+, your config, hooks and signing.
- History
- Branches and merges as a colored lane graph. Undo, revert, reset, check out or tag.
- Branches
- Merge, rebase, and pull with fast-forward, merge or rebase.
- Conflicts
- Resolve block by block, then continue, skip or abort.
- Pull requests
- Read, review in the same diff viewer, create, merge and check out.
- Issues
- Open, edit, comment, close and reopen, without the browser.
- Shortcuts
- Every action has one, every one can be rebound. Hold ⌘ to see them.
Questions.
What is GitViber?
A free, open-source git client for macOS and Linux, made for coding with agents. Run Claude Code, Codex or any other agent in parallel worktrees, watch their diffs land live, browse the code, test it in a built-in terminal and commit, all in one ~14 MB app.
Is it free?
Yes. It's open source under the GPL-3.0, with no account, no telemetry and no paid tier.
How do I run several Claude Code or Codex agents in parallel?
Give each agent its own git worktree: a separate folder on its own branch, so they don't step on each other. In GitViber you start one from any branch, commit or pull request, open a terminal in it and start the agent there. The top bar switches between worktrees and shows each one's change count.
Does it work with Claude Code and Codex?
It works with any agent that edits files in a folder: GitViber watches the worktree, not the agent. For commit messages it can run claude -p or codex exec for you, with no API key.
How is it different from GitHub Desktop?
GitViber is built around worktrees and agents: diffs that refresh the moment an agent saves, a terminal and a file explorer in the same window, and review progress kept per worktree. It's also ~14 MB; GitHub Desktop is 681 MB.
Do I still need an editor like Cursor or VS Code?
Not to review what an agent wrote. GitViber has whole-file diffs with word-level highlights, a file explorer with quick open and a terminal. Editors like Cursor easily take gigabytes of RAM just to let you read.
Does it use a lot of RAM or CPU?
No. It's a ~14 MB app with no bundled Chromium: a Rust core and the system webview. It idles at 0% CPU and wakes up only when files change. Activity Monitor can show memory climbing while you click around; that's memory WebKit hasn't collected yet, and it drops after a few idle minutes.
Which platforms does it run on?
macOS 13 or later, as one universal app for Apple Silicon and Intel, and Linux x86_64 as a .deb, .rpm or AppImage. macOS is used daily; the Linux builds are tested in CI. Windows is untested and has no build yet.
How do I sign in to GitHub?
There's no sign-in of its own. Run gh auth login once, or have git remember a github.com login, and GitViber borrows it. The token stays in memory.
Does it send anything anywhere?
It talks to your git remotes and, for pull requests and issues, GitHub. It checks GitHub Releases for updates, which you can turn off in Settings. Errors go to a local log file and nowhere else.
More in the README.
Close the other windows.
Free and open source. No account, no telemetry.
brew install --cask emircan-sahin/tap/gitvibermacOS 13 or later, one universal app, signed and notarized.
Linux x86_64: .deb, .rpm, AppImage. Needs git 2.36 or newer.