jj (Jujutsu)

Raised as a usability problem by 12 people on Hacker News over 4 years (2023–2026), in 11 threads.

People raised many different problems with jj (Jujutsu), but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 13 complaints

Using JJ as a Git frontend with mixed-tool teammates is not ideal2026-07-14
Confusing GUI that makes it very easy to rewrite history accidentally2026-04-14
Using jj to go back to an earlier change was frustrating and risked losing good files2026-04-10
Branch handling confusing; 'jj ls' output hard to follow and commits seemed to abandon branches2025-12-05
Using jj co-located with a Git repo caused a huge mess2025-12-05
Existing jj GUIs show only unified diffs and require typing rebase commands instead of dragging changes2025-11-11
Rebase model requires thinking about commit graphs and many suboptions for routine patch stacking2025-10-23
Hunk selection UI isn't natural to the commenter, mainly due to keyboard shortcuts2025-10-23
Jj's blame command is painfully slow, so the commenter falls back to git blame2025-10-13
Must recreate merge commit manually after fetch, seems like too much boilerplate2025-02-12
Editing a commit in the graph makes every change apply to descendants, making the tool modal2025-02-04
After running jj split user is dropped into unfamiliar text interface and feels lost2024-11-30
Output is cluttered with decorative art and colors, hard to read and missing key information2023-08-01