Tired of Electron Git clients eating your RAM? TyeGit is built in Rust + Tauri — it uses your OS's native WebView, so it's fast, lightweight, and actually fun to use. ✦ Edit the Git index directly before committing ✦ Fast-forward enforced by default — no messy merges ✦ GitHub Actions CI/CD status built into the branch view ✦ Retro Famicom UI that doesn't look like enterprise software Open-source. Free. Try it 👉 github.com/VesperAkshay/tyegit
No reviews yetBe the first to leave a review for TyeGit
Maker
📌
Hey everyone I'm Akshay, the solo dev behind TyeGit.
I started this project out of genuine frustration. I wanted a Git client that felt as precise as the terminal but didn't require me to memorize 40 flags. Every existing GUI either oversimplified things or ran on Electron and made my laptop sound like a jet engine.
A few things I'd love your honest take on:
The God-Mode editor — does editing the Git index directly before committing feel intuitive, or does it need better onboarding?
The Famicom UI love it or too much? I made a deliberate choice to not look like every other dev tool. Curious if it lands.
Performance especially on large repos. I'd love to hear if the Rust/Tauri approach actually feels faster in practice for you.
Windows binaries are ready to download right now at github.com/VesperAkshay/tyegit takes 30 seconds to install.
Ask me anything about the architecture, the design decisions, or the roadmap. I'll be in the comments all day.
Report
The ability to edit the Git index before committing caught my eye—what's the most common workflow where users find that better than interactive staging from the CLI?
Honestly the biggest one is commit hygiene after a long session.
You've got a dirty working tree bug fix, refactor, and a leftover console.log all tangled together in the same file. git add -p gets you there but it's a blind y/n hunk walk with zero spatial awareness. You're essentially navigating a diff in airplane mode.
The God-Mode editor drops you into a visual index state where you can cherry-pick exact lines, rewrite the stray debug line directly in the index without touching the working file, and see your staged vs unstaged state side by side. The commit that goes out is clean not "I'll squash it later" clean, actually clean.
Three workflows where it clicks most:
Splitting a messy WIP branch into two atomic commits before opening a PR
Patching a debug line out of the index without a follow-up "remove console.log" commit polluting the history
Final pre-push sanity check where you're reading exactly what's going into HEAD
It's basically git add -p but with spatial context and an escape hatch to edit in place. Same power, less archaeology.
The ability to edit the Git index before committing caught my eye—what's the most common workflow where users find that better than interactive staging from the CLI?
@farrukh_butt1
Honestly the biggest one is commit hygiene after a long session.
You've got a dirty working tree bug fix, refactor, and a leftover console.log all tangled together in the same file. git add -p gets you there but it's a blind y/n hunk walk with zero spatial awareness. You're essentially navigating a diff in airplane mode.
The God-Mode editor drops you into a visual index state where you can cherry-pick exact lines, rewrite the stray debug line directly in the index without touching the working file, and see your staged vs unstaged state side by side. The commit that goes out is clean not "I'll squash it later" clean, actually clean.
Three workflows where it clicks most:
Splitting a messy WIP branch into two atomic commits before opening a PR
Patching a debug line out of the index without a follow-up "remove console.log" commit polluting the history
Final pre-push sanity check where you're reading exactly what's going into HEAD
It's basically git add -p but with spatial context and an escape hatch to edit in place. Same power, less archaeology.