Skip to main content

Jj

@taylor/jjv2026.10.11.1· 2d agoBEHAVIORSACCEPTED WARNINGS
01README

Install and configure Jujutsu (jj) on Linux, macOS and Windows: with Homebrew or winget when they are there, otherwise from the GitHub release with its SHA-256 checked. Set user.name, user.email and any other user-level config, changing only keys that differ and restoring the file if jj rejects a value. uninstall removes only the jj it installed. sync reports the installed version and drift from the arguments.

02Behaviors1
@taylor/jj/cliv2026.10.11.1jj_cli.ts

Global Arguments

ArgumentTypeDescription
installMethod?enumauto (Homebrew on macOS and winget on Windows when available, otherwise the GitHub release), release, brew or winget
version?stringjj version to install: "latest" or a version like 0.46.0. Homebrew cannot pin one.
installDir?stringWhere the release method puts jj. Defaults to ~/.local/bin, or %LOCALAPPDATA%\\Programs\\jj on Windows.
jjPath?stringPath to a jj binary to use instead of looking for one
userName?stringuser.name for commits
userEmail?stringuser.email for commits
settings?recordOther user-level config, keyed as jj names them, e.g. {"ui.default-command": "log", "ui.diff-formatter": ":git"}
fn install(upgrade?: boolean)
Install jj if it is missing or not the pinned version; with upgrade, also bring it to the latest release
ArgumentTypeDescription
upgrade?booleanWith version "latest", also upgrade a jj that is already installed
fn uninstall()
Remove the jj this model installed (the release build, or the Homebrew or winget package); a jj installed any other way is left alone
fn configure()
Set user.name, user.email and the other settings in jj's user config, changing only keys that differ
fn sync()
Read the installed jj and its config without changing anything, recording drift from the arguments

Resources

installation(infinite)— Where jj is installed, its version and how it got there
config(infinite)— The managed user-level jj config values
03Stats
A
93 / 100
Downloads
1
Archive size
32.2 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License1/2partial

    no SPDX license declared

  • Verified public repository2/2earned

05Platforms
06Labels