Skip to content

Using jk

jk manual

Inspect and edit Jujutsu repositories from a terminal interface.

Use the log to select changes and inspect their contents. Rebase, squash, and restore show the affected revisions before you confirm; New and Edit run immediately.

Open your first repository

Follow a workflow

  1. 01 Start with a repositoryOpen jk, read the graph, choose revisions, and understand when an action changes history.
  2. 02 Inspect changes and compare contentReview the graph, revision details, diffs, file changes, and a change's evolution.
  3. 03 Create and reshape changesDescribe, create, edit, abandon, squash, and restore changes with explicit operands.
  4. 04 Move work with rebaseChoose a source scope, a destination, and a placement before rewriting the graph.
  5. 05 Name changes and check remotesCreate, move, and delete local bookmarks, fetch an explicit remote, and inspect a push dry-run.
  6. 06 Work across workspace directoriesInspect, add, rename, update, and forget jj workspaces.
  7. 07 Inspect results and recoverFind executed commands, inspect repository operations, and undo or redo with context.
  8. 08 Run commands with retained outputUse noninteractive jj and external commands, inspect their output, and recognize tool handoff limits.
  9. 09 Adjust one command's executionControl working-copy updates, historical execution, and immutable protection on a pending mutation.

Look up a command

Find a command's keys, options, and effects in the command reference. Entries distinguish native actions, commands run with :, and commands that require a separate terminal.

Recorded workflows

Watch rebase, bookmark, and recovery examples in disposable repositories. Each recording includes screenshots, terminal text, and checks of the resulting repository.

Current boundaries

jk 0.3.0 includes whole-change rebase, squash, and restore previews, bookmarks and remotes, workspace management, command history, and operation recovery. Native partial-change editing, conflict resolution, and real push remain gaps. The UX findings describe the evidence and proposed improvements.