← Back to BLACKWIRE GHOST BUREAU TECH SHIFT Terminal window showing Jujutsu command output alongside Git log

Sample output from `jj log @` demonstrates how Jujutsu displays commit and change IDs in a Git repository.

JUJUTSU VCS LAUNCHES AS GIT ALTERNATIVE FOR DEVS

*Ethan Lowman's Jujutsu Primer, posted November 18, 2026, outlines a new version‑control system that sits beside Git. It promises automatic rebasing, native undo and a workflow that keeps bookkeeping out of developers' heads.*

By GHOST Bureau - BLACKWIRE  |  November 20, 2026, 11:00 CET  |  Jujutsu, version control, Git alternative, automatic rebase, native undo

On November 18, 2026, developer Ethan Lowman published a concise guide titled “Jujutsu Primer.” The article introduces Jujutsu, a version‑control system that claims to simplify and extend the Git experience. Lowman argues that jj’s primitives are easy to learn yet powerful enough to enable workflows that Git makes cumbersome. Features such as automatic rebasing and native undo aim to reduce the mental load of tracking changes. The guide promises that developers can test jj inside any existing Git repository, offering a low‑risk path to adoption. By the end of the primer, readers see concrete command‑line examples that illustrate how jj records commits, manages change IDs, and keeps the working copy in sync without manual steps.

What is Jujutsu and why does it matter?

Jujutsu (jj) is a version‑control system designed for developers already familiar with Git. Lowman describes it as a set of simple primitives that compose into powerful workflows. Automatic rebase and native undo smooth the sharp edges of Git, letting users experiment with stacked diffs without mental overload. The system tracks revisions the same way Git does, but adds change IDs that remain stable as the logical change evolves. By exposing the shortest unique prefixes of IDs, jj reduces typing friction. The guide positions jj as a tool that can boost effectiveness by keeping VCS bookkeeping out of working memory.

How does Jujutsu integrate with existing Git workflows?

Jujutsu can run side‑by‑side with Git in the same repository. After installing jj, the command `jj git init` synchronizes jj and Git state automatically. From that point, developers can continue using familiar Git commands while jj records each change as a commit. The commit IDs match Git's SHA‑1 hashes when the Git backend is used, ensuring compatibility with existing tooling. Lowman shows that a working copy marked with @ is automatically committed, turning a manual `git commit` into an implicit jj action. This tight coupling lets teams adopt jj incrementally without abandoning their Git history.

“Personally, I think jj considerably boosts my effectiveness, because it allows me to keep VCS bookkeeping out of my working memory.”

Installation and configuration: step‑by‑step

Lowman lists four common installation paths. macOS users run `brew install jj`. Arch Linux users use `pacman -S jujutsu`. NixOS users launch `nix-shell -p jujutsu` from the unstable channel. Developers who prefer source builds need a recent Rust toolchain and execute `cargo install --locked --bin jj`. Once installed, `jj git init` boots the repository. Global user details are set with `jj config set --user user.name "Some One"` and `jj config set --user user.email "someone@example.com"`. The configuration file, written in TOML, can be edited via `jj config edit --user`. Scopes include `--repo` and `--workspace`, and the merged view is displayed with `jj config list`.

Core commands and workflow examples

The primer walks through typical jj commands. `jj log @` displays a graph with commit IDs (hex hashes) on the right and change IDs on the left. Short prefixes like `k` or `2` uniquely identify entries. `jj show 2` reveals commit metadata and diffs, as Lowman demonstrates with a config change. Creating a new file triggers an automatic commit: after editing `main.py`, `jj show` shows a new commit ID `66b59f20` and the diff. `jj status` reports the working copy state, while `jj diff` mirrors `git diff`. The system highlights that the working copy marker (@) disappears once the change is committed, confirming the automatic commit behavior.

Frequently asked questions

How can I try Jujutsu without leaving Git?

Install jj, run `jj git init` in an existing Git repository, and the two systems will synchronize automatically, letting you experiment side‑by‑side.

What platforms support Jujutsu installation?

macOS via `brew install jj`; Arch Linux via `pacman -S jujutsu`; NixOS via `nix-shell -p jujutsu`; and any system with Rust via `cargo install --locked --bin jj`.

What are change IDs and how are they used?

Change IDs are stable identifiers for logical changes that evolve over time; they appear on the left side of `jj log` output and can be referenced by their shortest unique prefix.

Lowman's primer positions Jujutsu as a pragmatic upgrade for developers entrenched in Git. By automating rebases and committing on the fly, jj promises to free mental bandwidth for code, not version‑control logistics. The side‑by‑side design means teams can experiment without disrupting existing pipelines. If the workflow gains traction, the next wave of development could see fewer manual merge conflicts and a smoother path to complex diff stacks. The open‑source nature and multi‑platform install options lay the groundwork for rapid adoption across the software ecosystem.

Sources: [Hacker News – Jujutsu Primer by Ethan Lowman, https://ethanlowman.com/posts/jj-primer/]