Local Changes
Stage whole files or single hunks, write the message, then commit and push in one step.
RepoBeam 1.8.4Coding Sessions, rebuilt for AI agents
See what Git will do. Before it does it.
A Git client for Windows and Linux that shows the expected result of a history change before it runs, explains conflicts in plain words, and lets you review every change an AI agent makes — then keep it, commit it, or undo it.
AI writes code fast.
A Coding Session records every file an agent changes, so you review it before it stays.
Coding Sessions History is easy to break.Going back, combining commits and repairing a sync each show the expected result first.
Before/After previews Conflicts stop work.Both versions side by side, with where each came from, and a result you can check.
Guided conflictsCoding Sessions New in 1.8
Let agents write the code.
You decide what stays.
Start a session before you or an AI agent changes anything. RepoBeam saves a private restore point and lists every change as it happens. No branch to switch to, and no commits of its own.
Works alongsideClaude CodeCodexCursorGitHub CopilotGemini CLIyour own editor
RepoBeam watches the files in your repository, so there is no plugin to install. A session is a restore point and a review, not a security sandbox: agents still run with your normal permissions.
Read the Coding Sessions guide →Before/After previews
Change history
with the outcome in view.
Going back to a commit, combining commits and repairing a diverged branch all open a preview first: your commit graph as it is and as it is expected to be, and a plain list of what changes. Nothing runs until you confirm.
Go back without breaking what you shared
- Commits you already pushed stay put. RepoBeam restores their files as changes, or with a new commit.
- Work that only exists on your computer can move back, keeping newer changes as changes or staged.
- A private recovery point is saved before anything is rewritten.
Instead of
git reset --hard 7b5d87e
git push --forceTidy up before you share
- Ctrl-click neighbouring commits, right-click, and write one message for them.
- The preview crosses out the old commits and shows the new one in their place.
- The files at the tip of the branch stay exactly the same.
Instead of
git rebase -i HEAD~2Repair a branch that diverged
- When your branch and its remote both moved, see how the commits will line up.
- Put your commits after the remote ones, or replace the remote after amending, with every replaced commit named first.
- If someone pushes in the meantime, RepoBeam stops and replaces nothing.
Instead of
git pull --rebase
git push --force-with-lease
- Recovery pointsMoving a branch back, combining commits and force pushing each keep what they replace on your computer.
- Published work is protectedRepoBeam prefers a new commit over rewriting history that others may already have.
- Force push, only where it belongsIt lives inside Fix sync, names every commit it replaces, and asks you to confirm on shared branches.
- Actions named by what they doUndo with a new commit, Back to this commit, Fix sync. No flags to remember.
Guided conflict resolution
Two versions.
One clear decision.
When a merge, rebase, cherry-pick, undo or stash restore stops on a conflict, RepoBeam opens the resolver on its own. Both versions sit side by side with where each came from. Keep one, keep both, or write the result, then continue or cancel.
- 1Both versions, explained
Local is your version on this computer. Server is the version Git is bringing in.
- 2Choose or combine
Keep either version, or both, in one click.
- 3Edit the final result
A code editor with syntax highlighting. What you see is exactly what is saved and staged.
- 4Checked before saving
A file can’t be saved while conflict markers remain in it.
- 5Continue or cancel
Finish the operation, or cancel it and the branch returns to where it started.
Everyday Git
Everything you reach for daily,
in one calm window.
History that explains itself
A commit graph with branches and tags. Merge commits list the commits they brought in.
Stashes you can read
See every stashed file’s diff, then restore one file, or all of them.
Edit without leaving
Fix a line straight from a diff, a stash or a session, and go full screen when you need the room.
Branches at a glance
Ahead and behind for each branch. Switch, rename, publish, or delete one on the remote.
Light or dark
Both themes are designed with the same care, or follow your system.
And the rest
- Repository tabs
- Search commits, files and branches
- Tags, with messages
- Remotes: add, rename, change the URL
- Image diffs
- Undo with a new commit
- Cherry-pick
- Your Git name per repository
- Open a terminal in the repository
- Update notices
Built to be trusted
Your code stays yours.
- No account
Open a folder and start. There is nothing to sign up for.
- Anonymous analytics
On by default and easy to turn off. Never source code, repository names, file names, remotes or credentials.
- Your Git, your keys
The Windows, .deb and AppImage builds use the Git, SSH keys and credential helpers you already have.
- Free, including for work
On as many computers as you like. License
Guides
Short guides
for the moments that matter.
The hard moments in Git,
made clear.
Free for Windows and Linux. Open a repository you already have: there is nothing to import and no account to create.
- The snap includes Git, updates automatically, and guides access to private repositories through Linux permissions.
- The Windows, .deb and AppImage versions use the Git, SSH agent and credential helpers already on your computer.
- RepoBeam doesn’t upload your repositories. Git only talks to the remotes you configure. Privacy
Windows64-bit installer · Windows 10 & 11
Download
Linux AppImagePortable · no install · needs Git installed
Download
Linux · Ubuntu & Debian64-bit package · uses the Git on your computer
Download
Then install it from a terminal, in the folder it was saved to:
apt installs Git as well if it is missing. Then open RepoBeam from your applications.More ways to install on Linux Snap · AppImage · terminal
Snap StoreMost Linux distributions · Git included · automatic updates Open ↗The .deb and the AppImage use the Git, SSH agent and credential helpers already on your computer. The snap brings its own Git and asks before it reads your SSH keys.
Needs Git: Git for Windows on Windows. The snap includes Git.
FAQ
Questions,
answered.
Does RepoBeam replace Git?
No. RepoBeam runs Git itself: the copy installed on your computer, or the copy included in the snap. Your repository stays a normal Git repository that you can keep using from the terminal or any other tool.
Does it work with Claude Code, Codex, Cursor or Copilot?
Yes, alongside any of them. A Coding Session looks at the files in your repository rather than plugging into a particular tool, so it records changes from an agent, an editor or a script the same way. Start a session, let the tool work, then review what changed.
Is a Coding Session a sandbox?
No. A session is a restore point plus a live review of what changed. Agents and editors still run with your normal permissions and can read files, run commands or use the network. The session shows what changed in the repository so you can undo it or keep it.
Does RepoBeam upload my code?
No. RepoBeam never sends repository names, source code, file names, commit content, remotes or credentials. Anonymous analytics are on by default and can send the app version, operating system, install source and which RepoBeam features are used. You can turn them off anytime in Settings; when off, RepoBeam sends no analytics requests. Git communicates with the remotes you configure, such as GitHub or GitLab. The privacy page lists every analytics field and counter.
What if I change my mind after rewriting history?
Moving a branch back, combining commits and force pushing from Fix sync keep a private recovery point first, and undoing a file in a Coding Session keeps the undone changes so you can bring them back. RepoBeam also avoids rewriting published commits by default.
Can I force push?
Yes, when it makes sense: after you amend or combine commits you already pushed. It is a choice inside Fix sync, which names every commit that will be replaced and stops if someone pushed in the meantime.
How do private repositories work with the snap?
When you first use an SSH remote, RepoBeam opens its Linux permission page and asks for read-only access to the SSH keys already on your computer. Turn on “Access SSH keys,” return to RepoBeam, and continue. You can revoke the permission at any time, or use an HTTPS remote without granting it.
Is it free, and what do I need?
RepoBeam is free to use, including for work (license). On Windows, you need 64-bit Windows 10 or 11 with Git for Windows. On Linux, install the snap, which includes Git, or use the .deb (Ubuntu and Debian-based distributions) or the AppImage with Git installed. All builds are 64-bit.