Article URL: https://agentgit.co/
Comments URL: https://news.ycombinator.com/item?id=49761528
Points: 10
# Comments: 6
Article URL: https://gcve.eu/2026/09/18/introducing-patch2vuln-v1.0-streamlining-vulnerability-advisory-creation-from-git-patches/
Comments URL: https://news.ycombinator.com/item?id=49755804
Points: 2
# Comments: 0
Article URL: https://rickub.com/
Comments URL: https://news.ycombinator.com/item?id=49755312
Points: 24
# Comments: 20
Article URL: https://tokenstead.ai/guides/zcode-silent-git-history-upload
Comments URL: https://news.ycombinator.com/item?id=49752422
Points: 262
# Comments: 14
Article URL: https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain
Comments URL: https://news.ycombinator.com/item?id=49751769
Points: 3
# Comments: 0
Article URL: https://blog.ferstar.org/en/posts/zcode-silent-workspace-snapshot-upload/
Comments URL: https://news.ycombinator.com/item?id=49750640
Points: 2
# Comments: 0
Article URL: https://twitter.com/useblacksmith/status/2100590354915291400
Comments URL: https://news.ycombinator.com/item?id=49742645
Points: 4
# Comments: 1
Article URL: https://blog.manganin.dev/blog/reinventing-issue-tracking/
Comments URL: https://news.ycombinator.com/item?id=49738631
Points: 1
# Comments: 0
Article URL: https://github.com/thetrueshags/AgentLane
Comments URL: https://news.ycombinator.com/item?id=49734832
Points: 3
# Comments: 1
Article URL: https://tyler-johnson.github.io/fufu/
Comments URL: https://news.ycombinator.com/item?id=49731341
Points: 1
# Comments: 0
Article URL: https://www.olafalders.com/2026/09/16/git-worktree-gotchas/
Comments URL: https://news.ycombinator.com/item?id=49728190
Points: 4
# Comments: 0
I built ctx to give agents a way to do a fast local search over previous session transcripts.
But I wanted to also give them a way to immediately surface "which agent wrote this exact line of code".
So you can start with a commit, a file, a line, or a PR, and then deterministically surface the exact tool call that wrote it, and the full agent transcript from that session.
It's really useful when you want your agents to know why code was written the way it was. It's kind of like a "super comment".
A normal code comment does leave some information about why code is the way it is.
But if you have selective access to the full original transcript, you can see everything about the code's provenance (like what tests were run, what was the reason it was there in the first place, etc)
This type of information would be way too verbose for a human to find useful. But agents can just ingest this stuff and make great use of it.
I like to instruct the agents to delegate this type of research work to cheaper high-throughput subagents like Luna for example.
Comments URL: https://news.ycombinator.com/item?id=49727859
Points: 3
# Comments: 2
Article URL: https://github.com/ctxwitch/ctxwitch
Comments URL: https://news.ycombinator.com/item?id=49727366
Points: 1
# Comments: 1
Article URL: https://www.tigrisdata.com/blog/objgit-packfiles/
Comments URL: https://news.ycombinator.com/item?id=49714411
Points: 7
# Comments: 0
Article URL: https://rewic.in
Comments URL: https://news.ycombinator.com/item?id=49713696
Points: 2
# Comments: 1
Article URL: https://github.com/stagas/livediff
Comments URL: https://news.ycombinator.com/item?id=49712345
Points: 6
# Comments: 3
Article URL: https://mmt.dev/
Comments URL: https://news.ycombinator.com/item?id=49711744
Points: 3
# Comments: 0
Article URL: https://devopscycle.com/blog/the-ultimate-git-cheat-sheet
Comments URL: https://news.ycombinator.com/item?id=49709591
Points: 3
# Comments: 1
This is timelapse of a 3D city simulation based on your Git history, files are buildings and height is based on LOC. Weather can determines if the repo is quiet or active during a span of time.
Just a fun visual to get the momentum overview of your project. I've been working a lot in 1 repo for the past few months and got a handsome amount of commits, so I decided to make something visually appealing to 'appreciate' my work somehow.
Based on the ideas of: CodeCity (Richard Wettel & Michele Lanza) and Gource (Andrew Caudwell, 2009). Instead of static city like CodeCity or 2D tree like Gource, chronocity is an 3D interactive city and you can even drive car in there lol.
All in the browser, TypeScript + three.js, isomorphic-git in a Web Worker, WebCodecs for the video.
It scans your .git folder (all client-sided, nothing uploaded) and through the main branch (downscaled to 2000 steps for big repos), compares files, LOC with previous step. three.js renders all the buildings in one instanced mesh, and height is the square root of LOC. The weather is not random: the sky follows the local time (their time zone) of people that commited, fog indicates quiet stretches, rain means a burst of changes in a short window.
Try your own project straight in my GitHub page, drop your Git cloned repo there (containing .git folder, all in your browser, your repos are stored in YOUR cache, this is serverless).
Comments URL: https://news.ycombinator.com/item?id=49708188
Points: 1
# Comments: 2
Article URL: https://codeberg.org/mergiraf/mergiraf
Comments URL: https://news.ycombinator.com/item?id=49706303
Points: 5
# Comments: 1
Article URL: https://github.com/jquinteiroo/devrecap
Comments URL: https://news.ycombinator.com/item?id=49704194
Points: 3
# Comments: 0
Article URL: https://github.com/overment/limen
Comments URL: https://news.ycombinator.com/item?id=49700087
Points: 5
# Comments: 0