GitAgent overview
wip76 releases

GitAgent release notes

Every released version of GitAgent, newest first, with what changed in it — written at the moment the release was cut, not reconstructed afterwards.

Turns a dirty working tree into an open pull request, one approved step at a time. Scans your repo, drafts a commit message and a PR description with a local ollama model or DeepSeek, then commits, pushes, and opens the PR — but nothing touches git history or the remote without an explicit yes at each gated step.

Current version

Version 0.1.78, released 3 October 2026. This is what the download buttons below install.

Added

  • The home screen checks the repositories in each recent folder and says what is waiting before you open it — uncommitted work, a pull request ready to merge or failing its checks, a release due — with a count for each. Hover a label to see which repositories it means.
macOS (Apple Silicon)Linux x86_64Windows

Free: work with 5 repositories. Pro: every repository, in every folder, for personal or professional use. Every build is produced by release CI and served from mayorana.ch.

All versions

GitAgent 0.1.77

Added

  • The diff a step shows has the same Copy button in its top-right corner, so the whole diff can go on the clipboard in one click.

Changed

  • A step's output log is taller and follows new lines as they arrive, so a long-running command no longer needs scrolling to watch. Scroll up to read something and it stays where you left it until you scroll back down.

GitAgent 0.1.76

Added

  • In the Branches panel, a branch with an open pull request has a Review & merge button that opens Review → Merge on that pull request.

Changed

  • More finished-with branches are marked "nothing new" with Clean up: a branch with no commits the base branch lacks, and one still exactly at what its merged pull request merged — including one named main in a repository whose base is master. A branch with an open pull request is never offered for clean-up.

GitAgent 0.1.75

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.74

Added

  • A Copy button in the top-right corner of a step's output or error log puts the whole log on the clipboard, so you can paste it into an issue or a chat without selecting it by hand.

GitAgent 0.1.73

Changed

  • Only one flow runs in a repository at a time. While a commit is under way, merging a pull request in the same repository waits until it is done, and the other way round; before, both could start and step on each other's branch switches and pulls in the same folder. The Branches panel follows the same rule: deleting, cleaning up or opening a pull request for a branch waits for a running flow, and no flow starts until that branch is done. Hover the greyed-out button to see what is in the way. Other repositories are unaffected.
  • Delete all merged in the Branches panel now deletes the branches one after another instead of all at once, and lists every branch it could not delete rather than only the last one.

GitAgent 0.1.72

Added

  • GitAgent now shares anonymous usage statistics, and it is on by default. A note at the bottom of the window tells you once, and nothing is sent until you have seen it. Turn off there, or Settings at any time, stops it for good. What is shared: which steps ran and whether they succeeded, your operating system, the GitAgent version, and whether the repository is on GitHub or Azure DevOps. What is never shared: repository names, folders, code, commit messages, branch names or error text. It is tied to a random number kept on your computer, not to you, and turning it off deletes anything that has not been sent yet. It also stays off if DISABLE_UPDATE_CHECK, DO_NOT_TRACK or GITAGENT_NO_TELEMETRY is set.

Fixed

  • Setting DISABLE_UPDATE_CHECK in your shell profile now also applies when GitAgent is opened from the Dock or Finder, not only from a terminal.
  • A release no longer runs on an out-of-date copy of the branch. If a pull request was merged on GitHub and not yet pulled, the release used to see no new commits and no notes, and offered to ship build-only, which would have released that change with no notes. GitAgent now pulls those commits first, before drafting notes or running your release script. If it can't pull them safely, it stops and offers the pull on a button.
  • When a release is held up for missing notes while origin has commits this copy lacks, GitAgent offers to pull them and release again, instead of offering a build-only release.
  • When your release script commits and tags a version but its push is rejected, GitAgent now explains that nothing reached origin and offers one button that undoes the local release commit and tag, pulls, and releases again. Before, only Retry, Skip and Cancel were offered, and retrying could not succeed.
  • "Back to base" no longer stops with "cannot lock ref" when another program, such as your editor's background fetch, updates the same branch at the same moment. GitAgent tries again on its own. If the other program is still busy, GitAgent explains that the repository is fine and offers to fetch again on a button, instead of "No automatic fix for this".

GitAgent 0.1.71

Changed

  • The window's title bar says when GitAgent Pro is active — "GitAgent · version · ✦ Pro" — and "Pro updates ended" for a licence whose updates have run out. It updates as soon as a licence is added or removed.

GitAgent 0.1.70

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.69

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.68

Changed

  • With GitAgent Pro active, the top-right corner of the window shows a ✦ PRO badge instead of a plain "Pro ✓" button. Hovering it shows who the licence is for and until when updates are included; clicking it still opens the licence window. A licence whose updates have ended shows ✦ RENEW PRO.

GitAgent 0.1.67

Changed

  • Without GitAgent Pro, GitAgent now works with 5 repositories in all, across every folder and every window. The first repositories listed take the 5; every other one is shown greyed out with a 🔒 Pro tag, isn't checked, and can't be selected, so no flow or branch action can reach it. Clicking a locked repository opens the Pro window, where it can take the place of one of your 5, or where you paste your licence key to unlock them all.

GitAgent 0.1.66

Changed

  • The refresh button at the top of the repository list is bigger and tinted green, so the check you run most often is the easiest one to hit. Its icon turns while the repositories are being re-checked.

Fixed

  • Bring the base in, offered when a pull request cannot be merged, now finishes the job when the base merges in cleanly: it pushes the branch, waits for GitHub to recheck the pull request, and asks to merge again. Before, a clean merge ended the run without a word and without pushing, so the pull request still showed as conflicting. A real conflict still stops before anything is pushed, with the files to fix marked.

GitAgent 0.1.65

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.64

Changed

  • A flow created in Setup is shown only on the repository you opened Setup from, instead of on every repository. In the other repositories the flow list button counts it as "1 more", and the list offers it as "only on other repositories — tick to add here". Setup says where each flow is shown, with Show on every repository for a flow meant for all of them, and Only on to restrict an existing one — which also covers repositories cloned later, unlike hiding it one repository at a time.

Fixed

  • When a pull request cannot be merged because it conflicts with the base branch, Bring the base in now switches to the pull request's own branch before merging the base into it. Before, it merged into whichever branch happened to be checked out. The button no longer reads "Abandon", and the message lists every step from there to a merged pull request.

GitAgent 0.1.63

Added

  • GitAgent Pro. The free version now runs flows in 5 repositories of your choice: the first run in a repository takes one of the 5, and Get Pro… in the top bar shows which ones and lets you give one back. Every repository stays listed and checked as before; once the 5 are taken, the others show a Pro tag and a run there opens the Pro window instead of starting. Paste the licence key from your purchase email in the same window to run flows in every repository. The key is checked on your computer, with no account and nothing sent anywhere.

GitAgent 0.1.62

Added

  • The Branches panel spots branches that are ahead of the base branch but would change no file if merged — old merge commits, or work the base already has from a squash merge — and marks them "nothing new". A Clean up button closes the branch's open pull request and deletes it on GitHub and locally, after a confirmation. Before, such a branch was listed as needing a pull request, and one named main offered no action at all.

GitAgent 0.1.61

Fixed

  • Refresh in the repository list now looks at the folder again: a repository cloned into it since it was opened appears, and one deleted or moved away disappears. Before, it only re-checked the repositories already listed, and a new one needed the folder to be reopened.
  • Committing in a repository with no commits yet — straight after git init — works. Scan changes used to fail with "ambiguous argument 'HEAD'". The first commit now goes on the branch you are on and is pushed as that branch, with no pull request, since the remote has nothing yet to open one against.

GitAgent 0.1.60

Added

  • The update check now considers preferred formats for each operating system, ensuring a more tailored download experience.

GitAgent 0.1.59

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.58

Fixed

  • A flow's steps are listed in the order they run. Steps added in Setup in front of an existing one used to appear at the bottom of the run view, after the step they come before, even though Setup showed them in the right place.

GitAgent 0.1.57

Fixed

  • A large change no longer makes a local model lose its instructions and run until the 15-minute timeout. What a step sends is now sized to the model's context window, and every answer has a length limit, with a local model or an API key alike.
  • When a diff is too large, whole files are left out rather than the diff being cut mid-file: lock files first, then docs and CI, then the largest code files. The step's log names what the model did not see.
  • The context window in Settings now shows how much of a diff it allows. Lower it for faster answers on large changes.

GitAgent 0.1.56

Fixed

  • A push rejected because GitHub still has a branch of the same name from an already merged or closed pull request now says so, and offers to push under a new name. The pull request then opens under that name too. Before, the only fix offered was pulling the old branch in, which mixed its commits into your change.

GitAgent 0.1.55

Added

  • A release with no notes in CHANGELOG.md no longer stops at the script. The model drafts the notes from what changed since the last release, and you read and approve them before they are added and committed. A release that only touched CI, scripts or docs gets a "no user-visible change" line without asking the model. Flows that run release.sh get the two new steps added in front of it once; remove them in Setup if you don't want them.

Fixed

  • A commit no longer lands on a branch named like one still on GitHub from an earlier, merged pull request. The push used to be rejected as "behind its remote counterpart", with pulling the old branch in as the only offered fix.

GitAgent 0.1.54

Fixed

  • A release that stops because CHANGELOG.md has no notes now explains the two ways forward and offers to release as build-only, with no notes, in one click. Before, it said "no automatic fix" and left you to rerun the script in a terminal.

GitAgent 0.1.53

Fixed

  • A fix offered from a failed step, such as closing a pull request, now runs inside the repository it is for. Run from anywhere else, gh pr close 11 could close #11 of a different repository.
  • An open pull request that no longer changes any files is reported as such, with an offer to close it, instead of the sidebar showing "ready to merge" with no way forward.

GitAgent 0.1.52

Fixed

  • Reviewing a pull request whose branch is already fully merged into its base says there is nothing to review instead of failing.

GitAgent 0.1.51

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.50

Fixed

  • With a local Ollama model, draft steps now queue for the model one at a time and show as queued, instead of all starting at once and timing out while they waited their turn.

GitAgent 0.1.49

Added

  • Trust all in the top bar: every repository and every flow runs trusted, answering its own approvals, until you turn it off. Turning it off lets a run already in progress finish its current flow before asking again.

Changed

  • The sidebar's action buttons are larger and show a tooltip.

GitAgent 0.1.48

Added

  • A banner at startup for occasional messages from us, such as a request for feedback. It is fetched once from mayorana.ch, stays until you dismiss it and is not shown again after that. If the notice cannot be fetched, no banner appears and startup is not slowed.

GitAgent 0.1.47

Added

  • A flow picker in the workspace, to show or hide a repository's flows without leaving the page.

GitAgent 0.1.46

Changed

  • Larger, better-spaced buttons in the repository sidebar. The old ones were too small to hit reliably.

GitAgent 0.1.45

Added

  • Flows can be hidden per repository. A hidden flow is not offered there and a trusted run does not use it.

GitAgent 0.1.44

Fixed

  • Clearing a flow's name in Setup no longer leaves an unnamed flow in the sidebar; it becomes "Untitled flow".
  • Setup fields for names, commands and branches no longer autocorrect, capitalise or spell-check what you type.

GitAgent 0.1.43

Added

  • Flow edits in Setup are kept as a draft until you save. Save is enabled only when something changed, and Cancel asks before discarding your edits.

GitAgent 0.1.42

Added

  • A first-run screen that asks what writes the commit messages: a model on this machine, a hosted API, or none. It preselects what it finds, and a hosted API key is kept for the session only. With no model, GitAgent builds a plain commit message from the list of changed files.

GitAgent 0.1.41

Added

  • Skip on a step that is waiting or running, to move past one that is slow or not needed this time. A trusted run carries on past a skipped step.

Changed

  • Clearer messages when a model call times out or fails.

GitAgent 0.1.40

Changed

  • Large diffs open and scroll much faster. Each diff is highlighted once instead of on every redraw.

Fixed

  • Unchecking every file at the commit approval no longer commits the files you unchecked. An empty selection now means nothing is staged.
  • Branch names generated from a commit message are always valid, even when a cut lands on a dot or produces .. or .lock.
  • Files with spaces or unusual characters in their paths are staged correctly.

GitAgent 0.1.39

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.38

Added

  • The app's icon in the window title bar and taskbar.

GitAgent 0.1.37

Changed

  • A repository whose commit flow just opened a pull request and switched back to the base branch still shows that pull request as waiting. GitAgent now looks at every open pull request, not only the checked-out branch's.

GitAgent 0.1.36

Changed

  • The list of files to commit is shown by default at the commit approval, instead of hidden behind an unlabelled toggle.

GitAgent 0.1.35

Added

  • A trusted run that stops says why: which step needs a person, or that no flow answers what the repository needs next.
  • Stop asking me on an approval: approves that step and every later one in the repository, turning the run you started into a trusted run. It still stops at a merge the analysis or CI is unhappy about.
  • Setup marks a flow that answers no repository need, since nothing will ever start it.

GitAgent 0.1.34

Added

  • A tally at the top of the sidebar: how many repositories are running, have a failed run, or need something from you.

GitAgent 0.1.33

Added

  • The sidebar marks repositories whose last run failed, and each repository has a button to check it again without refreshing the whole list.

GitAgent 0.1.32

Fixed

  • A trusted run no longer stops at the commit flow because the new pull request's checks are still pending. It moves on to the review.

GitAgent 0.1.31

Changed

  • A trusted run now works through the repository rather than one flow: after a commit it moves on to the review, then the release, re-checking the repository between each, and stops when something needs a person.
  • The test step is added to your existing commit flows too, between scanning and committing, keeping your own settings and steps. If you remove it, it stays removed.

GitAgent 0.1.30

Added

  • Trusted run: a flow answers its own approvals and stops only at a step that needs a person, showing why it stopped there.
  • A test step in the commit flow that runs the project's own test command before anything is committed. GitAgent detects the command.

GitAgent 0.1.29

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.28

Added

  • A banner when a newer version is available.

GitAgent 0.1.27

Added

  • Flows that are no longer valid are listed with what is wrong, and cannot be started until they are fixed.

GitAgent 0.1.26

Changed

  • Opening the review flow selects the pull request that needs reviewing, instead of leaving you to pick it.

Fixed

  • The base branch is worked out the same way everywhere. The sidebar and the flows could disagree about what a branch was compared against.

GitAgent 0.1.25

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.24

Changed

  • The Windows installer installs for the current user by default, with no administrator prompt. Administrators can still install for every user from the command line.

GitAgent 0.1.23

Added

  • GitAgent detects a rebase, merge, cherry-pick or revert left unfinished, shows it in the sidebar with the conflicted files, and offers to finish it once everything is resolved, or abandon it and go back to where you were.

GitAgent 0.1.22

Added

  • A push rejected because the branch is behind its remote offers to pull first.

GitAgent 0.1.21

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.20

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.19

Changed

  • A pull request with merge conflicts now offers to bring the base branch into it and resolve the conflicts in a terminal, before offering to abandon it.

GitAgent 0.1.18

Fixed

  • On macOS, notifications no longer ask which application should show them each time one is raised.

GitAgent 0.1.17

Added

  • Flows declare which repository needs they answer (uncommitted changes, an unpushed branch, an open pull request, a release due), chosen in Setup. The workspace opens the flow that answers what a repository needs, whatever the flow is called.

Changed

  • A step you reject now shows as declined rather than failed.

GitAgent 0.1.16

Changed

  • The sidebar shows a running, waiting or failed run ahead of what the repository needs next.

Fixed

  • A release that was due could be hidden behind an open pull request with pending checks.

GitAgent 0.1.15

Added

  • A system notification when a run stops and needs you, only while the GitAgent window is in the background.

GitAgent 0.1.14

Fixed

  • Long repository names are shortened in the workspace instead of pushing the buttons off their row. The full name shows on hover.

GitAgent 0.1.13

Fixed

  • GitAgent picks up the environment variables from your login shell, such as API keys and tokens, so commands behave as they do in a terminal when the app is started from the Dock or Start menu.
  • Command output is shown without stray colour codes.

GitAgent 0.1.12

Changed

  • Downloads and update checks now come from mayorana.ch instead of GitHub.
  • GitAgent is source-available under the PolyForm Noncommercial licence: free for personal, educational and noncommercial use.

GitAgent 0.1.11

Added

  • A spinner on a branch while deleting it or opening a pull request for it, with its buttons disabled until the action finishes.

GitAgent 0.1.10

Added

  • The sidebar shows merged work that has not been released yet.

Fixed

  • Only open pull requests are offered for review. A merged or closed one could be picked and then fail.

GitAgent 0.1.9

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.8

Fixed

  • GitAgent uses your login shell's PATH, so gh, az, cargo and other tools are found when the app is started from the Dock or Start menu.

GitAgent 0.1.7

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.4

Added

  • A Target branch setting for pull requests, for repositories that merge into something other than their default branch, such as develop. Left empty, GitAgent detects it.

Fixed

  • Clearer errors when fetching the base branch fails.

GitAgent 0.1.3

Changed

  • Packaging only — no user-visible change.

GitAgent 0.1.2

Added

  • Review any open pull request on a repository, not only the one for the checked-out branch, with several reviews in progress at once. The sidebar shows how many pull requests each repository has open.
  • A syntax-highlighted diff view, with a preview of the pull request's diff before anything runs. Showing the diff is a step you approve.
  • A step waiting for your approval is marked in the graph.
  • Output from push and other remote commands streams in as it happens.
  • Flows can be shown or hidden per repository.
  • A pull request with merge conflicts offers to abandon it.

Fixed

  • A failure to list pull requests (rate limit, network, sign-in) is shown as an error instead of looking like a clean repository.
  • The CI status step checks the pull request being reviewed, not the one for the checked-out branch.
  • Changes committed outside GitAgent are picked up, and the rest of the flow continues.
  • Long diffs scroll instead of being squeezed to fit.

GitAgent 0.1.1

Added

  • First release: turn a dirty working tree into an open pull request. GitAgent scans the changes, drafts the commit message and pull request description with a model, then commits, pushes and opens the pull request.
  • Nothing touches git history or the remote without your approval. Each gated step shows the exact commands it will run first, and only tracked files are committed.
  • Local Ollama or remote DeepSeek for the drafts.
  • A Setup screen with a flow editor.

The same history, as JSON

This page is generated from a feed published beside the builds — the same file GitAgent reads when it checks for an update. Point a script at it if you track versions across a team.

https://mayorana.ch/downloads/gitagent/latest/releases.json

Need it adapted to your work?

Each of these tools is built and maintained by us. If you need a variant — a different data source, your own conventions, a feature your team is missing, an on-prem build — that is the kind of work we take on.

Get in touch