Git 2.56.0 was released on September 28, 2026, with changes that improve conflict handling, history traversal, repository storage and branch cleanup. Several of the improvements are especially relevant to AI coding agents because agents can perform Git operations much more frequently than a human developer.
The release is not a single headline feature. It is a collection of smaller safety and performance improvements that can make large repositories easier to operate.
Safer conflict resolution with git add --resolved
Git 2.56 adds a new git add --resolved mode for staging paths that are currently unmerged. It is designed for the specific moment after a developer resolves a merge conflict.
The command also checks selected regular files for leftover conflict markers before staging them. That makes the workflow narrower than git add -u or git add -A, which can stage unrelated changes.
This is useful for coding agents because an agent may be working in a repository where the working tree contains changes it did not create. A narrower staging command reduces the chance of accidentally including unrelated edits.
Faster merge-base calculations
Git performs merge-base calculations for merges, three-dot diffs and other operations that need to understand shared history. GitHub reports that Git 2.56 can stop its search earlier when one side of the history can no longer produce another merge base.
GitHub describes large improvements in some real repositories, including a Linux kernel example where one merge-base operation dropped from 167,441 traversal steps to 3,887. The exact benefit depends on repository history, so teams should benchmark their own workloads.
Smaller repository packs with path-walk repacking
Git 2.56 removes two important restrictions around path-walk repacking: reachability bitmaps and delta islands. Path-walk repacking can group objects by their tree paths and find better delta relationships.
GitHub reports that one Fluent UI benchmark produced a 164.4 MB pack with path-walk compared with 558.5 MB using the benchmark's ordinary bitmap repack setup. That is a benchmark result, not a promise that every repository will see a similar reduction.
Branch cleanup is easier to automate
Git 2.56 adds a bulk form of git branch --delete-merged. It can match upstream patterns and local branch patterns, with --dry-run available to show candidates before deletion.
This matters for teams using coding agents because agent-generated branches can accumulate quickly. A controlled cleanup command can reduce branch sprawl without requiring a custom script that guesses which branches are safe to delete.
More useful history tools
The experimental git history command continues to expand. Git 2.56 adds a drop operation that removes a selected commit and replays its descendants onto the parent. It remains experimental and has restrictions, including limitations around merge commits.
Git also adds improvements to reference management through the git refs toolbox, a safer git bisect reset option, and better handling of partial-clone blobs.
Why Git performance matters for AI agents
An AI coding agent may inspect status, calculate diffs, switch branches, search history, run tests and create commits many times during one task. Small improvements in Git operations can therefore reduce repeated overhead across a long agent run.
More importantly, safer commands reduce the risk that an automated workflow changes more than intended. The best agent integrations should prefer narrow, explicit operations and inspect the resulting status before moving to the next step.
How to test Git 2.56 in an agent workflow
- Run your normal merge and conflict-resolution tasks against a test repository.
- Measure merge-base and diff operations on representative repositories.
- Test branch cleanup with
--dry-runbefore enabling deletion. - Check how your automation handles unrelated working-tree changes.
- Measure repository size before and after any repack experiment.
- Keep experimental Git commands away from production automation until they pass your own tests.