{"id":588545,"date":"2026-05-17T06:26:13","date_gmt":"2026-05-17T06:26:13","guid":{"rendered":"https:\/\/www.newsbeep.com\/uk\/588545\/"},"modified":"2026-05-17T06:26:13","modified_gmt":"2026-05-17T06:26:13","slug":"git-is-unprepared-for-the-ai-coding-tsunami","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/uk\/588545\/","title":{"rendered":"Git is unprepared for the AI coding tsunami"},"content":{"rendered":"<p>Last month, Mitchell Hashimoto, HashiCorp co-founder, <a href=\"https:\/\/mitchellh.com\/writing\/ghostty-leaving-github\" rel=\"nofollow noopener\" target=\"_blank\">publicly declared<\/a> that he was moving his popular open source Ghostty terminal emulator project from GitHub. GitHub runs the world\u2019s largest service built on the Git distributed version control system, created by Linus Torvalds.<\/p>\n<p>Once an enthusiastic user, <a href=\"https:\/\/www.theregister.com\/software\/2026\/04\/29\/mitchell-hashimoto-says-github-no-longer-for-serious-work\/5227505\" rel=\"nofollow noopener\" target=\"_blank\">Hashimoto grew disillusioned<\/a>\u00a0with\u00a0service disruptions, and <a href=\"https:\/\/mitchellh.com\/writing\/github-changesets\" rel=\"nofollow noopener\" target=\"_blank\">increasingly slow pull requests<\/a>. \u201cThis is no longer a place for serious work if it just blocks you out for hours per day, every day,\u201d he wrote.\u00a0<\/p>\n<p>Hashimoto was quick to defend Git itself: \u201cThe issue isn&#8217;t Git, it&#8217;s the infrastructure we rely on around it: issues, PRs, Actions, etc.\u201d<\/p>\n<p>Many have\u00a0<a href=\"https:\/\/www.theregister.com\/columnists\/2026\/05\/05\/microsofts-code-shack-shaken-as-redmond-chases-ai-ghosts\/5219761\" rel=\"nofollow noopener\" target=\"_blank\">blamed<\/a>\u00a0GitHub\u2019s performance on Microsoft, which acquired the company in 2018. But to be fair, GitHub itself has been experiencing heavier-than-expected traffic thanks to a proliferation of AI-generated pull requests. <\/p>\n<p>In 2025, GitHub<a href=\"https:\/\/github.blog\/news-insights\/octoverse\/typescript-python-and-the-ai-feedback-loop-changing-software-development\/\" rel=\"nofollow noopener\" target=\"_blank\"> saw a 206 percent year-over-year growth<\/a> in AI-generated projects measured by the use of Bash shell scripts, a widespread way of running agents. And more AI code means more bugs. Research from GitClear<a href=\"https:\/\/altersquare.medium.com\/your-team-ships-2x-more-pull-requests-since-adopting-ai-your-bug-count-also-doubled-87e636494115\" rel=\"nofollow noopener\" target=\"_blank\"> found<\/a> that AI-generated code heaped 10.83 issues per pull request, compared to 6.45 for the old-fashioned human variety.<\/p>\n<p>Our new agentic workforce is raising big questions about how the entire software development lifecycle (SDLC) should evolve, and if Git should come along.\u00a0<\/p>\n<p>\u201cAgents are nudging us toward a continuous flow,\u201d warned <a href=\"https:\/\/www.linkedin.com\/in\/peco-karayanev\/\" rel=\"nofollow noopener\" target=\"_blank\">Peco Karayanev<\/a>, co-founder of DevOps platform provider<a href=\"https:\/\/www.autoptic.ai\/solutions\" rel=\"nofollow noopener\" target=\"_blank\"> Autoptic<\/a>, which bridges Git-based deployments with observability tools for agent-based remediation. <\/p>\n<p>Autoptic\u2019s entire user base runs on some form of Git, either homebrew or from a service provider like GitLab.\u00a0<\/p>\n<p>Given the volume and magnitude of changes across repos, \u201cwe need git to start operating in a more continuous mode,\u201d Karayanev wrote in an email interview.<\/p>\n<p>Git operations, especially when used in GitOps-style automated deployments, still need to be managed by people. Updates, commits, pushes, merges are often yoked into sequences of \u201cstop\/go\u201d episodes where someone has to hit enter on the keyboard a few times to continue the workflow, Karayanev noted. This model may not hold up once agents start getting priority.\u00a0<\/p>\n<p>A butler for Git<\/p>\n<p>Git has always had its share of critics, especially those who use the tool daily.\u00a0<\/p>\n<p>There may not be another piece of software that is so widely adopted and yet so inscrutable. Torvalds and other Linux kernel developers built <a href=\"https:\/\/github.com\/gitster\/git\" rel=\"nofollow noopener\" target=\"_blank\">Git<\/a> in 2005 after frustrations with trying to shoehorn Linux code into the commercial BitKeeper tool. Linux, a global group project of mammoth proportions, required a distributed version control system able to support non-linear development of thousands of parallel branches.\u00a0<\/p>\n<p>Like any distributed system, Git can be difficult to understand.<\/p>\n<p>One of the co-founders of GitHub, <a href=\"https:\/\/www.linkedin.com\/in\/schacon\/\" rel=\"nofollow noopener\" target=\"_blank\">Scott Chacon<\/a> co-wrote a book on using Git (2009\u2019s <a href=\"https:\/\/git-scm.com\/book\/en\/v2\" rel=\"nofollow noopener\" target=\"_blank\">Pro Git<\/a>) and still he finds himself occasionally flummoxed by the version control system.<\/p>\n<p>There are still \u201csharp edges\u201d to Git, Chacon told The Register. \u201cThere&#8217;s a lot of stuff that it doesn&#8217;t do very well from a usability standpoint,\u201d he said.\u00a0<\/p>\n<p>Chacon co-founded <a href=\"https:\/\/gitbutler.com\/\" rel=\"nofollow noopener\" target=\"_blank\">GitButler<\/a> as a way to \u201crethink the porcelain\u201d of Git, to make Git more suitable to modern workflows. (Last month, GitButler <a href=\"https:\/\/blog.gitbutler.com\/series-a\" rel=\"nofollow noopener\" target=\"_blank\">received $17 million<\/a> in venture capital funding).\u00a0<\/p>\n<p>Think of GitButler as a super-powered Git client. It allows the developer to work on two different branches simultaneously, using a technique called virtual branching. It reconciles the code a developer is working on with the upstream code. They can reorder commits, or edit the comments of a previous commit. It offers richer metadata about the files being worked on. It can show which commits are unique to that branch. <\/p>\n<p>Best of all, it eliminates what many developers call \u201crebase hell,\u201d where merges into an updated codebase must be checked one at a time, a problem GitButler solves by keeping the user\u2019s code synchronized with what is upstream. <\/p>\n<p>Many of these actions GitButler offers can be done through the Git command itself \u2013 although Git\u2019s command language, and its rules, can be so obtuse that \u201cyou will probably make a mistake at some point,\u201d Chacon said.<\/p>\n<p>A Git for agents<\/p>\n<p>Chacon believes GitHub\u2019s current reliability issues stem from the current tsunami of agentic work.\u00a0<\/p>\n<p>This is \u201cironic\u201d because GitHub was built to scale Git, he said. \u201cBut an influx of agents is pushing the service to the brink.\u201d<\/p>\n<p>The problem lies not with Git itself, but with everyone using one service, Chacon argued. Last year, GitHub had about 180 million users working across 630 million repositories \u2013 with 121 million created in 2025 alone, according to the company\u2019s most recent annual <a href=\"https:\/\/octoverse.github.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Octoverse<\/a>\u00a0report.\u00a0<\/p>\n<p>\u201cFrom the longer-term perspective, it doesn&#8217;t need to be like this,\u201d he argued. Maybe Git should be run locally, mirrored globally and managed with clients \u2026 such as GitButler, Chacon suggested. Perhaps Git-based version control systems could be customized for specific industry verticals.\u00a0<\/p>\n<p>We need to think about how we \u201cdistribute these systems more,\u201d he said. \u201cGit is designed to be distributed but we\u2019re not distributing it,\u201d he said.<\/p>\n<p>GitButler has created a command line interface specifically for agents. It was designed to give <a href=\"https:\/\/www.theregister.com\/software\/2025\/04\/21\/a-friendly-introduction-to-mcp-the-usb-of-ai\/1105570\" rel=\"nofollow noopener\" target=\"_blank\">MCP<\/a> servers an integrated map of the repository, which otherwise would require stitching together multiple Git commands. The Virtual Files concept allows the agent to work on a section of code that is also being worked on by a developer, or another agent.<\/p>\n<p>These are changes that point to a rethinking of how a Git workflow should run.\u00a0<\/p>\n<p>\u201cI think all of these systems should fundamentally change, because all of our workflows have changed, right? There needs to be different, sort of primitives for how to deal with these problem sets,\u201d Chacon said.\u00a0<\/p>\n<p>A tip from gaming development<\/p>\n<p>One company that wants its platform to replace Git altogether is <a href=\"https:\/\/www.diversion.dev\/about\" rel=\"nofollow noopener\" target=\"_blank\">Diversion<\/a>, which has built an eponymous distributed version control system initially pitched for large-scale game design.<\/p>\n<p>\u201cGit&#8217;s architecture is actually an issue that prevents scaling,\u201d argues Diversion CEO <a href=\"https:\/\/www.linkedin.com\/in\/sasha-medvedovsky-10b2381\/\" rel=\"nofollow noopener\" target=\"_blank\">Sasha Medvedovsky<\/a>\u00a0in an interview with The Register. \u201cFundamentally it&#8217;s an architecture problem that can&#8217;t be fixed and is a bottleneck for end users and hosting services.\u201d<\/p>\n<p>Git is a distributed system insofar as every user, or hosted service, requires a dedicated database (much like blockchain). \u201cIt&#8217;s not distributed in the regular sense but rather replicated,\u201d he wrote in an exchange with The Register on LinkedIn.\u00a0<\/p>\n<p>Operations run on a single thread, making concurrent operations impossible. As a result, the larger the repository, the slower the commit operations \u2013 a deadly combination for fast-paced agentic software development, Medvedovsky noted.\u00a0<\/p>\n<p>Of course, every CEO will have their talking points ready about a competitor\u2019s weaknesses (Diversion is<a href=\"https:\/\/diversion.dev\/blog\" rel=\"nofollow noopener\" target=\"_blank\"> finalizing a blog post<\/a> with hard numbers about Git and GitHub performance). But there are a growing number of other initiatives around prepping Git for the challenging times ahead.<\/p>\n<p>Perhaps most notable is <a href=\"https:\/\/github.com\/jj-vcs\/jj\" rel=\"nofollow noopener\" target=\"_blank\">Jujutsu<\/a>, a Git-compatible distributed version control system, stewarded by Google senior software engineer Martin von Zweigbergk. Like GitButler, Jujutsu (jj) aims to eliminate a lot of the annoyances that come with Git. It includes an undo button and the ability to keep committing even when there is a conflict.\u00a0<\/p>\n<p>And because everything written in C must be recast into Rust these days, long-time Git contributor <a href=\"https:\/\/github.com\/Byron\" rel=\"nofollow noopener\" target=\"_blank\">Sebastian Thiel <\/a>started a project called <a href=\"https:\/\/github.com\/Byron\" rel=\"nofollow noopener\" target=\"_blank\">Gitoxide<\/a>\u00a0to rebuild Git in Rust. Potential benefits include significant <a href=\"https:\/\/kx.cloudingenium.com\/en\/gitoxide-ein-gix-fast-git-implementation-pure-rust-guide\/#summary\" rel=\"nofollow noopener\" target=\"_blank\">performance improvements<\/a> through multicore processing, and the <a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2025-48384\" rel=\"nofollow noopener\" target=\"_blank\">much-needed memory safety<\/a> that comes with Rust.\u00a0<\/p>\n<p>Will Git 3 solve all the problems?<\/p>\n<p>Git\u2019s chief maintainer is <a href=\"https:\/\/github.blog\/open-source\/git\/celebrating-15-years-of-git-an-interview-with-git-maintainer-junio-hamano\/\" rel=\"nofollow noopener\" target=\"_blank\">Junio Hamano<\/a>, who took the reins from Torvalds in 2005. And he remains busy keeping Git current. <\/p>\n<p>At FOSDEM this February, core Git contributor and GitLab engineering manager <a href=\"https:\/\/github.com\/pks-t\" rel=\"nofollow noopener\" target=\"_blank\">Patrick Steinhardt<\/a>\u00a0<a href=\"https:\/\/fosdem.org\/2026\/schedule\/event\/HTJK33-evolving_git_for_the_next_decade\/\" rel=\"nofollow noopener\" target=\"_blank\">discussed<\/a> some of the changes coming in the next version of Git, version 3, which is gradually being rolled out this year.\u00a0<\/p>\n<p>One of the chief improvements will be in the way Git manages the commit references, the IDs that point to each change being made. Surprisingly, this operation is a real bottleneck for the software. \u201cThe design is inefficient,\u201d Steinhardt told the audience.<\/p>\n<p>Every time a programmer commits a code change, it gets recorded in a \u201cpacked-refs\u201d file, which saves time by not giving each commit its own reference file.\u00a0<\/p>\n<p>As projects grow larger, however, it takes longer for Git to amend or to delete a reference in packed-refs (One GitLab repo has a packed-refs file of more than 20 million references, Steinhardt said).\u00a0<\/p>\n<p>This is especially problematic when you have multiple, simultaneous readers and writers of that file. And just forget about getting a consistent view of all the references.\u00a0<\/p>\n<p>The freshly implemented Reftable feature, which will be the default in Git 3.0, stores references in an indexable binary format. The Git folks borrowed this concept from the Eclipse Foundation\u2019s <a href=\"https:\/\/projects.eclipse.org\/projects\/technology.jgit\" rel=\"nofollow noopener\" target=\"_blank\">JGit <\/a>Java implementation of Git.\u00a0<\/p>\n<p>Reftable allows for block updates, eliminating the need to rewrite a 2 GB-sized file for a single entry. And it is much faster for reading, which would pave the way for Git supporting larger, more sprawling repositories \u2013 perfect for an ever-busy agentic workforce.<\/p>\n<p>For nearly two decades, Git has proved to be the version control system of choice for geeks worldwide. But even with these new features and various third-party enhancements, can it retain relevance for a new generation of agentically enhanced coders?\u00a0<\/p>\n<p>The battle is on.\u00a0\u00ae<\/p>\n","protected":false},"excerpt":{"rendered":"Last month, Mitchell Hashimoto, HashiCorp co-founder, publicly declared that he was moving his popular open source Ghostty terminal&hellip;\n","protected":false},"author":2,"featured_media":588546,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[554,733,4308,86,56,54,55],"class_list":["post-588545","post","type-post","status-publish","format-standard","has-post-thumbnail","category-artificial-intelligence","tag-ai","tag-artificial-intelligence","tag-artificialintelligence","tag-technology","tag-uk","tag-united-kingdom","tag-unitedkingdom"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts\/588545","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/comments?post=588545"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts\/588545\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/media\/588546"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/media?parent=588545"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/categories?post=588545"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/tags?post=588545"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}