GitViber

Vibe code from one app.
Run your agents in parallel worktrees, watch their diffs land live, browse the code, test it in the terminal and commit, without GitHub Desktop, an editor and three terminal windows open.

Download for macOS or Linux · Install · What's new

Coding with agents turned the day into reading code. You start Claude Code or Codex in a few worktrees, then juggle an editor to look at the files, GitHub Desktop to see the diffs, a pile of terminals to run things and a browser for the pull requests. Editors like Cursor easily eat gigabytes of RAM just to let you read.

GitViber is one window for all of it, and it's small:

• 14 MB app. GitHub Desktop is 681 MB. No bundled Chromium, a Rust core and the system webview.
• Idles at 0% CPU. It wakes up when files change, not on a timer.
• Memory it gives back. Activity Monitor also counts memory the app is done with but WebKit hasn't collected yet, so the number climbs while you click around and drops again after a few idle minutes. Closing a terminal frees its GPU memory at once.
• Fast on big diffs. Diffs are computed in Rust and highlighted off the main thread.
• Plain git underneath. Your config, hooks, credentials and signing. Nothing of its own goes into the repo.

Give every agent its own worktree and switch between them from the top bar, each with its change count, its pull request and how its checks are doing. Start one from any branch, commit or issue, in the folder you choose, or check a pull request out into its own worktree without touching yours. A new worktree can run a command such as claude in its terminal right away, and gets copies of the ignored files .worktreeinclude lists, like your .env. Rename one along with its folder, lock it, and remove or prune it when the work is merged. Every worktree keeps its own terminals, so nothing gets lost when you hop between them, and a terminal can open in another project or any folder too. A tab and its worktree show a ring while Claude Code works there, and a dot once it finishes or asks for you, with a desktop notification if you turned those on. Other agents get the dot when they ring the terminal bell or send a notification. Quit with Claude Code, Gemini CLI or opencode still running, and the restored terminal has the command that resumes the conversation typed at the prompt.

Diffs refresh the moment an agent saves, without losing your scroll position. Unified or split, word-level highlights, unchanged lines folded away until you want the whole file (⌥C). A changed image shows side by side, as a swipe or as an onion skin. J / K walk the changed files and V marks one viewed; when the agent touches it again, the mark clears so you know to look again.

A real terminal sits under the diff (��J), with tabs and splits. Run the tests, start the dev server or talk to the agent without leaving the change you're reading. Each pane of a split has a title bar with what runs there, and ⌘R names it. The terminal has its own font, size, cursor and scrollback in Settings, and ⌘= / ⌘− in the terminal or a pinch over it size its text. ⌘-click a path it prints to open the file at that line, or a folder to show it in the explorer. In zsh and bash 4.4+ each command gets a mark, red when it failed, ⌘↑ / ⌘↓ jump between them, and the last one's output copies from the right-click menu; your dotfiles stay as they are.

It's made for agents too: paste a screenshot or drop files and Claude Code or Codex gets their paths, Shift+Enter reaches them as its own key, and on a Mac a trackpad swipe scrolls Claude Code's fullscreen view row by row, as it does vim and htop.

A full file explorer with change bars in the gutter, quick open (⌘P) and rename, create and delete from the right-click menu. Fix a line right in the file view and save it with ⌘S. For most days that's the editor you no longer need open.

Turn it on in Settings, hit the sparkle next to the commit box, and your own claude -p or codex exec writes the message from the diff. New pull request has the same button for the title and description. No API key, no extra account: it uses the CLI you're already signed in to.

Eleven color themes for the whole app, from Nord and Catppuccin to Solarized, 24 syntax themes, your own code font, terminal font and interface scale. Every action has a shortcut, every shortcut can be rebound in Settings, and holding ⌘ shows them all.

Grab the latest build from Releases:

Or with Homebrew:

brew install --cask emircan-sahin/tap/gitviber

On Linux:

sudo apt install ./GitViber_*_amd64.deb          # Debian, Ubuntu
sudo dnf install ./GitViber-*.x86_64.rpm         # Fedora
chmod +x GitViber_*.AppImage && ./GitViber_*.AppImage

To open a repository from a terminal, run gitviber . (or any path inside one); a file opens in the code view, at a line with gitviber src/app.ts:42 or :42:7. Homebrew and the Linux packages put the command on your PATH; otherwise use Install 'gitviber' Command in the app menu (File on Linux). A folder dropped on the Dock icon opens too.

GitViber tells you when a new version is out. The macOS app and the AppImage update in place; a .deb or .rpm install gets a link to the release to download it from. What changed is in the changelog, and every release lists SHA-256 checksums in SHA256SUMS.

GitViber is used daily on macOS. The Linux builds are tested in CI, but the app itself is only starting to get used there (#35). Windows is untested and has no build yet.

• git 2.36 or newer. GitViber runs your own git, and says so on first launch if it's missing or older. On macOS, xcode-select --install or Homebrew's git will do.
• Optional: the GitHub CLI (gh auth login) for pull requests and issues; git's stored github.com credential works too. claude or codex if you want commit messages written for you.

You need Rust (stable), Node 22+, pnpm and git.

git clone https://github.com/emircan-sahin/gitviber && cd gitviber
pnpm install
pnpm install:mac    # macOS: builds a release and copies it into /Applications
pnpm tauri build    # Linux: makes a .deb, an .rpm and an AppImage

On Linux, Tauri's webview also needs WebKitGTK 4.1 and a C toolchain:

sudo apt install libwebkit2gtk-4.1-dev build-essential        # Debian, Ubuntu
sudo dnf install webkit2gtk4.1-devel gcc                       # Fedora
sudo pacman -S --needed webkit2gtk-4.1 base-devel              # Arch

If the AppImage step fails in linuxdeploy (its bundled strip is too old for current toolchains, e.g. on Arch), run it with NO_STRIP=true.

No telemetry, no API keys. The app talks to your git remotes and, for pull requests and issues, GitHub. For those it borrows a login you already have, the GitHub CLI (gh auth token) first, then git's stored github.com credential, and keeps the token in memory. GitViber checks GitHub Releases for updates at launch and every few hours; turn it off in Settings → Updates. Errors, including every error message the app shows you (a failed push's git output, say), go to a local file (~/Library/Logs/app.gitviber.desktop/errors.log on macOS, Help → Show Logs) and nowhere else, with logins in URLs and GitHub tokens blanked out. Help → Copy Diagnostics copies only the versions of GitViber, the OS, git, gh and WebKit, for you to paste into a bug report. Markdown from GitHub is cut down to GitHub's own HTML allowlist, and an image hosted outside GitHub loads only when you click it. Commit message suggestions go wherever the command you picked sends them.

Will macOS say it "can't be opened" or "is damaged"? Not for a release: the app is signed with a Developer ID and notarized by Apple. If it does, the download didn't come from Releases or was changed on the way; check it against SHA256SUMS and download it again. A build of your own isn't notarized, but it's already trusted on the Mac that built it.

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 (any HTTPS push does), and GitViber borrows it. See Privacy.

Where are the logs? Help → Show Logs. They're at ~/Library/Logs/app.gitviber.desktop/ on macOS and ~/.local/share/app.gitviber.desktop/logs/ on Linux. Help → Copy Diagnostics copies the versions a bug report needs.

Where are my settings? In the app's own storage, never in your repositories: ~/Library/WebKit/app.gitviber.desktop on macOS, ~/.local/share/app.gitviber.desktop on Linux.

How do I uninstall it? On macOS, drag GitViber to the Trash (or brew uninstall --cask --zap gitviber, which also removes its settings, caches and logs). On Linux, sudo apt remove git-viber or sudo dnf remove git-viber, or delete the AppImage. To remove the settings by hand, delete the folders above and ~/Library/Caches/app.gitviber.desktop.

Tauri 2 and Rust on the backend, React 19 with Radix and Tailwind v4 on the front. Diffs are computed in Rust with similar, highlighting is Shiki in a web worker, and the UI runs in the system webview, so there's no bundled Chromium.

pnpm tauri dev      # run the app (takes the next free port if 1420 is in use)
pnpm check          # what CI runs: build, tests, rustfmt, clippy

Bug reports and small, focused PRs are welcome. CONTRIBUTING.md covers setup and the few rules the app depends on. Report security issues privately, see SECURITY.md.

GPL-3.0. Use it, change it, share it; a fork you ship has to stay open under the same license.