Questions, answered.

No. wyrm is built so you can get useful work done before jj fully clicks — the log graph, diffs, and push preview read like any good git GUI. As you go, jj’s ideas surface naturally. And if you’ve never touched jj, the git → jj tutorial is the fastest way in.

No. jj is Git-compatible — it reads and writes ordinary git repositories. wyrm works with your existing repos on GitHub, GitLab, Bitbucket, or anywhere else. Your teammates can keep using plain git; nothing about your history changes underneath them.

It’s smaller than git, not bigger. jj drops the staging area, the detached HEAD, the stash — the parts that trip people up — and replaces them with a handful of ideas that hold together. Most of the friction in git simply isn’t there. wyrm’s job is to make those ideas visible while you work.

macOS today, as a native app. Linux and Windows are coming — wyrm is built cross-platform from the ground up, so it’s a question of polish and packaging, not a rewrite.

No. wyrm is local-first. Your repositories, diffs, and history stay on your machine — nothing is sent to a server to make the app work. The only network traffic is to your own git remotes when you fetch or push, plus a lightweight sign-in. More detail on the security page.

One repository, forever — no trial timer, no nag screen. Pro unlocks unlimited repos and a few power features. The full breakdown lives on the pricing page.

Reach out on the contact page — it’s one person reading the other end, so real answers, not a ticket queue. Bugs and feature requests are welcome too.

Start in the documentation. If you’re coming from git, the git → jj tutorial maps the commands you already know onto their jj equivalents — the fastest path from “I use git” to “I get jj”.