We're making Git hosting more reliable, performant, and scalable. This post traces 20 years of Git infrastructure and explains how that history led us to design and operate our Git storage, Origin, as if it were a database. cursor.com/blog/git-at-an…↗

Signups are now open on Code[dot]Storage. Today, more new repos are created per second on Code Storage than any other platform. Lovable, Bolt, Amp, Poke, and many more of the largest agentic workloads store their code and agent memory at scale using Code.Storage.↗

our work on git will go to upstream, in the C programming language, so long as they are useful generally. so, a public fork.↗

42 is the answer to everything. This is @EntireHQ’s answer to Git in the era of agents: fast, independent, distributed. Mirror your GitHub repos, let your agents clone and pull from the region(s) of your choice, and…we're open sourcing it. 🤖↗

been thinking about why I don't feel comfortable with AI being a true personal assistant still, even though the models have gotten so much better. i realized a lot of the reason for me is actually git / version control. using an agent that is 99.999999% accurate vs 97% accurate…↗

Git push, to anywhere. Trunks turns any backend into a git remote. S3, R2, Tigris, MinIO, Postgres, SFTP, NFS, SMB, local disk, or a file share. Use git like normal. Trunks does the rest. Built for sandboxes, parallel agent runs, and handoffs before work becomes a GitHub PR. …↗

there's an interesting new trend with how interact with OSS i'll clone the repos & run them locally, whenever its missing a feature i'll just prompt it to add it did this with t3 code this weekend to add ssh support, cmd + k, fast mode now i have a set of patches i like and wa…↗

101 ⭐ on our @openclaw memory plugin! check it out here - git.new/molt-memory↗

Created an agent that runs on a weekly cron job, that fetches my weekly git history and turns it into a nice changelog. I love this way too much hazel.sh/changelog↗

New Cursor Rule: When provided with a git repo url, clone it into /tmp so it can be explored & understood↗

cursor pro tip for vibe coders: use the git tab to save changes and roll back quickly if the ai messes up seeing too many stories of vibe coders unable to get back to a working version 😰 watch the video↗

This saves me 5-10 seconds on each commit.↗

@ryolu_ @cursor_ai 100% yes. I also use git branches per feature I'm working on.↗