Show HN: I created a cross-platform GUI for the JJ VCS (Git compatible)

Hacker News (score: 51)
Found: October 20, 2025
ID: 1993

Description

Other
Show HN: I created a cross-platform GUI for the JJ VCS (Git compatible) Personally, I think the JJ VCS (https://github.com/jj-vcs/jj) hit a point some time in this past year where I find it hard to find a great reason to continue using git. Over the years I've cobbled together aliases and bash functions to try to improve my git workflow, but after using jj, which works with ~any git repo and integrates great with Github repos, all of the workflow issues I ran into with git are not only solved, but improved in ways I couldn't manage with simple scripts.

One example is the op log, which lets you go to any point in your repo's time and provides simple undo and redo commands when you want to back out of a merge, didn't mean to rebase, etc.

Because I have a pretty strong conviction that JJ is at this point a cleaner and more powerful version of git, my hopes are that it continues to grow. With that, it seemed a proper full-featured GUI was missing for the VCS. There's some plugins that add some integration into VS Code, and there's one in the works to get Intellij support working, but many of the constructs JJ provides in my opinion necessitate a grounds-up build of a GUI around how JJ works.

Right now, Judo for JJ is an MVP in an open beta. I did my best to support all of the core functionality one would need, though there's many nice-to-haves that I am going to add, like native merge support, native splitting, etc. Most of this will be based on feedback from the Beta.

I'm really grateful for the great community JJ has built, alongside the HN community itself in the countless VCS-based posts I've read over the years, and am hoping for lots of input here during Beta under real usage - the goal is to be a full-featured desktop GUI for the VCS, similar to many of the great products that are out there for git.

More from Hacker

Show HN: Offline tiles and routing and geocoding in one Docker Compose stack

Show HN: Offline tiles and routing and geocoding in one Docker Compose stack Hi HN,<p>I’m building Corviont, a self-hosted offline maps appliance (tiles + routing + search) for edge&#x2F;on-prem devices.<p>Hosted demo (no install): <a href="https:&#x2F;&#x2F;demo.corviont.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;demo.corviont.com&#x2F;</a><p>Self-host (Docker Compose repo): <a href="https:&#x2F;&#x2F;github.com&#x2F;corviont&#x2F;monaco-demo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;corviont&#x2F;monaco-demo</a><p>Docs: <a href="https:&#x2F;&#x2F;www.corviont.com&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;www.corviont.com&#x2F;docs</a><p>What’s inside:<p><pre><code> - Vector tiles served locally (PMTiles) - Routing served locally (Valhalla) - Offline geocoding&#x2F;search + reverse (SQLite Nominatim-based index) - MapLibre UI wired to the local endpoints </code></pre> After the initial image + data pulls, it runs fully offline (no external map&#x2F;routing&#x2F;geocoding API calls).<p>Next (if people need it): a signed on-device updater for regional datasets (verify → atomic swap → reload).<p>I’d love feedback: where offline maps&#x2F;routing&#x2F;search matters for you, and what constraints bite (hardware, fleet size, update windows, regions, deployment style).

Common Lisp SDK for the Datastar Hypermedia Framework

Common Lisp SDK for the Datastar Hypermedia Framework

No Graphics API

No Graphics API

Ghostty compiled to WASM with xterm.js API compatibility

Ghostty compiled to WASM with xterm.js API compatibility

No other tools from this source yet.