Neat project, but the README would benefit from a human author. I can tell what you prompted by the way the README is worded. It should tell me more about what this project solves. I don't care that it uses idiomatic zig. Why should I use this instead of lazygit?
In general, for most projects like this the README is the product. You usually have better results using it and the code as a starter prompt for your own software if you feel the need. I wouldn’t use this kind of thing directly from upstream.
If this is idiomatic zig, functions must be expensive because it fails horribly in the DRY departement. Also, papering over exceptions everywhere by... catching and not handling exceptions. What could possibly go wrong?
This is huge. I've always wanted to use Git in the terminal but never been happy with the underlying language that other TUIs were written in. Now that I know that I'm using developer-managed memory I can be much more comfortable and confident changing between branches, pushing, and pulling, and even merging code. Thanks Simone!
I've been using tig, written in C, for ages now, never once crashed. And I'm all for safe languages, but a git TUI isn't really as critical as you imply - if I interpreted the sarcasm correctly.
Very cool, but if I'm prompting / looping an AI agent as my main development process, what is the use case here? I feel the biggest help would be to make Reviewing PRs from the terminal easier, I care less about commit logs and status.
you can see the diff before you merge it. my main use case for lg is looking at diff and staging logical parts then committing with another tool or manually.
I’m such a CLANKER hater now, I want to know if this was written by agents or not. If written by agents, I don’t want anything to do with it. I only want human written software, even LLM autocomplete seems a bridge too far.
Hi HN, I've been building Ziggity, a keyboard-driven terminal UI for Git.
It's inspired by lazygit (which I used daily), but written from scratch in Zig rather than being a port.
Why another one? Two reasons, honestly. There were a few areas of lazygit I wanted to improve on for my own workflow, and I wanted a real project to build in Zig, which is genuinely powerful and fast, and a joy once it clicks. It compiles to a single small static binary with explicit memory ownership and no libgit2, it just shells out to the `git` you already have. The UI is built on libvaxis. And I let myself add a bit of sugar along the way, because a tool you stare at all day might as well be pleasant.
A few things that are a bit different from lazygit:
- A divergence view + status-coloured commit hashes so ahead/behind commits stand out at a glance
- Independent drill-downs in the Branches/Commits panels (deliberate, not a port artifact)
- Line level staging, interactive rebase, custom patch building, bisect, arbitrary-ref diffing
It's honest about its stage: v0.3.0, macOS/Linux/Windows builds, MIT. The Windows build compiles and libvaxis supports it, but I haven't smoke-tested it on real hardware yet. There's an about screen with a spinning ASCII donut, because why not.
Install: `brew install simoarpe/ziggity/ziggity`, or grab a static binary
from the releases page.
I'd genuinely appreciate feedback, especially on the UX and on the Zig code if you're into that. It's a spare time project, so bug reports and "this feels wrong" notes are welcome.
It's probably because of HN's anti-LLM filter. I don't know if submitters use LLMs to touch up their descriptions or if these descriptions often use LLM-like phrasing.
If that's what happened, I wonder if the same filters exist for tools like Grammarly. Some people are English as a second language, and some people simply want to put the best foot forward and make the best first impression.
Also lots of "genuinely" and some air quoted phrases which are another tell.
I guess you folks are right and it's probably the llm filter. I looked at the GitHub and thought it had too many screenshots to not have had some human effort, but who knows these days.
Neat project, but the README would benefit from a human author. I can tell what you prompted by the way the README is worded. It should tell me more about what this project solves. I don't care that it uses idiomatic zig. Why should I use this instead of lazygit?
In general, for most projects like this the README is the product. You usually have better results using it and the code as a starter prompt for your own software if you feel the need. I wouldn’t use this kind of thing directly from upstream.
If this is idiomatic zig, functions must be expensive because it fails horribly in the DRY departement. Also, papering over exceptions everywhere by... catching and not handling exceptions. What could possibly go wrong?
You have no idea don't you? it's like telling Ghostty failed because you don't understand how try/catch was a mistake in software conception.
Why are there exceptions in the first place then? If that's what you want, write ON ERROR RESUME NEXT and be honest about it.
This is huge. I've always wanted to use Git in the terminal but never been happy with the underlying language that other TUIs were written in. Now that I know that I'm using developer-managed memory I can be much more comfortable and confident changing between branches, pushing, and pulling, and even merging code. Thanks Simone!
I'm amazed at the comments on this.
lazygit works great and fast enough
This is just a copy of LazyGit the original and long player git in tui
I just use the regular git cli. Works fine.
I've been using tig, written in C, for ages now, never once crashed. And I'm all for safe languages, but a git TUI isn't really as critical as you imply - if I interpreted the sarcasm correctly.
you dropped your /s
prolly authored it in a tui and it crashed, since it wasn't written in rust
I wonder when is the 900,000 lines single commit coming for Rust rewrite
I'm working on porting the Rust compiler to VB.NET, so I can run it inside Excel spreadsheets.
And so it's "actually memory safe".
/sarcasm in case not obvious.
I really want someone to do this now.
Port it to PowerPoint!
It's written by Claude already so it probably wouldn't make any difference I guess?
You beat me to it
dont worry, soon or late it will show up in HN..
Very cool, but if I'm prompting / looping an AI agent as my main development process, what is the use case here? I feel the biggest help would be to make Reviewing PRs from the terminal easier, I care less about commit logs and status.
I actually made something that has that exact purpose, making reviewing easier. https://github.com/lnenad/difiko
you can see the diff before you merge it. my main use case for lg is looking at diff and staging logical parts then committing with another tool or manually.
I know what these words mean, but if I didn't this would be a whole lot of nonsense.
Maybe can emphasize yourself and call it LazyZig or something with the lazy moniker.
Lazy in a way that it was been vibe coded
i've always found magit better than any opinionated git terminal UI. Including LazyGit.
With Claude, i find myself reaching for Magit even less.
If Quagmire were in charge of naming things.
I like the Zig+Git+TTY portmanteau.
Need to change the logo to one of a guy with a massive chin and a creepy stare.
I like it but the donut animation is not needed, overbuilding gives AI slop vibes
I would love to use it without gimmicks.
Because it is, Claude is one of the two contributors. Just another slop project made farming HN points and marketing.
Honest feedback:
This is AI generated TUI slop made with claude.
I've been seeing a sad trend of these things being built with AI with no care and will be just abandoned in less than a month.
Why should I use this when I can use lazygit which is more popular and has been around and battle tested for years?
Exactly, waste of electricity
I’m such a CLANKER hater now, I want to know if this was written by agents or not. If written by agents, I don’t want anything to do with it. I only want human written software, even LLM autocomplete seems a bridge too far.
You can just scroll down to the contributors section to see that it was indeed written by Claude
Understandable
Yes, smells like vibe code. Haven't looked inside but can already tell
You're in for a great deal of pain in the coming years.
some of you all need to take a break from politics, it is clearly not doing you good and easy to get swept up into group mania imo.
So you guarantee that you yourself will never use AI or agents in any capacity?
Is that the principled position you want stand on in 2026 and beyond?
Yes I won’t use LLM autocomplete or agents for any personal projects. At work, I’ll do whatever’s needed.
> Yes I won’t use LLM autocomplete or agents for any personal projects.
So you would use AI including LLM autocomplete at work, but at the same time, you don't want anything to do with it?
You just previously said that:
>> "...If written by agents, I don’t want anything to do with it. I only want human written software, even LLM autocomplete seems a bridge too far."
That means you would still use AI at some capacity which breaks that guarantee.
This also means that you just contradicted yourself, when I explicitly said in any capacity that you would never use AI or agents at all.
i appreciate that it’s not more rust slop, but i never understood the need for a git frontend.
I started using lazygit a couple years ago, never looked back. It’s great
Hi HN, I've been building Ziggity, a keyboard-driven terminal UI for Git. It's inspired by lazygit (which I used daily), but written from scratch in Zig rather than being a port.
Why another one? Two reasons, honestly. There were a few areas of lazygit I wanted to improve on for my own workflow, and I wanted a real project to build in Zig, which is genuinely powerful and fast, and a joy once it clicks. It compiles to a single small static binary with explicit memory ownership and no libgit2, it just shells out to the `git` you already have. The UI is built on libvaxis. And I let myself add a bit of sugar along the way, because a tool you stare at all day might as well be pleasant.
A few things that are a bit different from lazygit: - A divergence view + status-coloured commit hashes so ahead/behind commits stand out at a glance - Independent drill-downs in the Branches/Commits panels (deliberate, not a port artifact) - Line level staging, interactive rebase, custom patch building, bisect, arbitrary-ref diffing
It's honest about its stage: v0.3.0, macOS/Linux/Windows builds, MIT. The Windows build compiles and libvaxis supports it, but I haven't smoke-tested it on real hardware yet. There's an about screen with a spinning ASCII donut, because why not.
Install: `brew install simoarpe/ziggity/ziggity`, or grab a static binary from the releases page.
Repo: https://github.com/simoarpe/ziggity
I'd genuinely appreciate feedback, especially on the UX and on the Zig code if you're into that. It's a spare time project, so bug reports and "this feels wrong" notes are welcome.
I can't really tell why this comment got flagged, so I've vouched it.
Maybe I've missed some context
It's probably because of HN's anti-LLM filter. I don't know if submitters use LLMs to touch up their descriptions or if these descriptions often use LLM-like phrasing.
If that's what happened, I wonder if the same filters exist for tools like Grammarly. Some people are English as a second language, and some people simply want to put the best foot forward and make the best first impression.
> - Independent drill-downs in the Branches/Commits panels (deliberate, not a port artifact)
> (deliberate, not a port artifact)
Smells like AI
Also lots of "genuinely" and some air quoted phrases which are another tell.
I guess you folks are right and it's probably the llm filter. I looked at the GitHub and thought it had too many screenshots to not have had some human effort, but who knows these days.
I actually made the same thing in Rust https://github.com/lnenad/difiko
Just FYI a large portion is vibecoded for those that don't like that.