Gitaur — a Git desktop client vibe-coded with Aurelia 2

Site Feedback
1

Hi everyone! I’ve just made Gitaur public—a Git desktop client vibe-coded in a couple of days, mostly for fun and to showcase what you can build with Aurelia 2.

It uses aurelia-headless, its Tailwind theme, and Tauri 2. GitExtensions inspired the commit graph and separate staging/commit window. There’s also syntax-highlighted diffs, an integrated merge editor, worktree support, and common branch and history operations.

It’s MIT licensed, with preview builds for Windows and Linux. It’s still an experiment, so expect rough edges! Feedback, bug reports, and contributions are welcome.

Source code · Downloads

5 Likes
2

The GitExtensions-style split between the commit graph and a separate staging/commit window is a sensible choice — I find that layout much clearer than cramming everything into one pane. The integrated merge editor and worktree support are also more than I’d expect from a quick experiment. Since you call it rough around the edges, which part do you feel needs the most attention first — the diff highlighting, or the branch/history operations? I’ll keep an eye on the repo.

3

Good question about priorities. I’d rather see the branch/history operations hardened first, since diff highlighting is mostly cosmetic if something looks off, whereas a misbehaving reset or history action costs real work. The GitExtensions-style split you mention is also what makes the staging window worth having, so keeping that flow predictable matters more than polish in the diffs. Curious whether you’re testing on Windows or Linux builds, as the rough edges may differ between them.

4

Agree that a botched reset or history action costs far more than imperfect diff colours, so hardening branch/history first seems the right call. On the platform question, I can’t speak to either build from use, but it’s worth asking whether the rough edges are in the Tauri layer itself or in the Git operations, since those failures would show up differently across Windows and Linux. If it’s the operations, platform shouldn’t matter much; if it’s Tauri, the reports will diverge and that’s useful to separate early.