Nit – I rebuilt Git in Zig to save AI agents 71% on tokens
Building a native git replacement optimized for AI agent consumption.
Nit – I rebuilt Git in Zig to save AI agents 71% on tokens launched on March 26, 2026 with 23 votes, #838 of 23,380 launches that month and more than 90% of that year's launches.
In plain words
Nit is a Git implementation written in Zig designed to reduce token consumption for AI agents. It rebuilds core Git functionality with a focus on efficiency, potentially decreasing token usage by 71% compared to standard implementations. The tool targets developers and AI systems that work with version control and need to optimize computational costs. Its Zig-based architecture emphasizes performance and minimal resource overhead.
written from the facts on this page · September 2026
From the sources
AI agents call git constantly. Status, diff, log, show. I pulled data from 3,156 real coding sessions and git accounted for roughly 459,000 tokens of output. That’s 7.4% of all shell commands. Codex is even worse (over 10% of its bash calls are git). Makes sense though right? git’s output was designed for humans. Verbose headers, instructional text, column padding, decorative formatting. It’s the informational equivalent of wrapping every answer in a gift bag with tissue paper. Machines don’t need the tissue paper or the gift bag. Every extra token costs money and adds latency. So I built nit. A native git replacement written in Zig that talks directly to the git object database via…from justfielding.com
Does a similar job
all alternatives →
Git for AI AgentsMay 2026 · github.com · ▲129hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
HexisAug 2026 · github.com · ▲169Git-backed control plane for AI-agent skills, tools, context, permissions, and identity. Self-hosted and MCP-native. - Bevel-Software/Hexis
GitAgent by LyzrMar 2026 · gitagent.sh · ▲231Hey HN, We built GitAgent — a git-native, framework-agnostic open standard for defining AI agents. The idea is simple: your repo IS the agent. npx @open-gitagent/gitagent@latest run -r https://github.com/shreyas-lyzr/architect -a claude That one command clones the repo, reads agent.yaml + SOUL.md + skills/, and launches it with Claude Code. Switch `-a openai` or `-a lyzr` to run the same agent on a different framework. No code changes. Goal: is keep the gitagent as a open standard ledger for an AI Agent in a VM, with versioned memories, skills etc. An agent is…
git-lrcFeb 2026 · hexmos.com · ▲300Hi HN, I'm the author of git-lrc, would appreciate some feedback from the community Last year my team started using AI coding tools more heavily, and we found ourselves generating tons of code, but spending less time looking at the stuff that's been generated. We felt like we were losing a bit of grip/understanding of what we were building. Regressions occasionally slipped through. Sometimes changes made it all the way to production only to be reverted later. We tried several AI code review tools, but most operate at PR time. That felt too late. I wanted review to happen while the…
I replaced vector databases with Git for AI memory (PoC)2025 · github.com · ▲198Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…

More ai this month
the category →



Paintings by AI models: programs run through a simulation of oil paint.
AI · 22d ago · stillwet.art

FastRouter.ai▲364Route requests to the right LLM for cost, latency & quality
AI · 23d ago · fastrouter.ai
Source: Show HN post ↗
Launched alongside, March 2026
the whole month →


Switch from ChatGPT to Claude with import memory feature
AI · Mar 2026 · claude.com
Littlebird▲709Littlebird remembers everything across your meetings, messages, docs, and apps, then takes action so you can recall any detail and never lose context.
AI · Mar 2026 · littlebird.ai

