Skip to main content

Is gji a fit?

Choose gji when you regularly leave one Git task open to work on another: reviews, features, investigations, or experiments. Its focus is giving those tasks separate directories and making them easy to return to from your shell.

Start with the job you need done​

Your needA useful starting point
Keep one task open and move to anothergji: create a worktree, run setup, enter it, and navigate back
Manage worktrees directly with Gitgit worktree: create, list, and remove linked working trees
Work through Git operations in a terminal UIlazygit: inspect and operate on your repository interactively
Clone and locate repository rootsghq: organize repositories on disk

These tools can complement each other. For example, locate a repository with ghq, enter a task with gji, then run lazygit inside that worktree. The table compares their focus, not benchmark results or exhaustive feature coverage.

What gji adds to Git worktrees​

Git provides the separate working trees. gji connects the routine steps around them:

  • gji new creates a branch and directory, runs supported dependency setup, and hands your shell to it.
  • gji pr 1234 fetches a GitHub PR into a separate working directory.
  • gji go finds open tasks, including across registered repositories.
  • gji back returns to the worktree you just left.
  • gji done and gji clean remove finished worktrees with state checks and prompts.

With shell integration loaded, this can be your interruption-and-return flow:

# Your feature is already open in its own worktree.
gji pr 1234
# Inspect and test the PR here.
gji back
# Continue your feature with its changes still in place.

Use a real PR number from your repository. New worktrees may need dependency installation; existing ones retain their own install state.

When your existing setup may be enough​

If you work on one branch at a time and rarely need a second working copy, another CLI may not help much. Raw git worktree may also be sufficient if you already have a path layout and scripts that handle setup and navigation well.

Costs and boundaries​

  • Each worktree uses disk space for its files and dependencies. First-time setup takes time.
  • Worktrees share repository history and refs. They don't isolate services, ports, or external data.
  • Shell integration is required to move the current shell automatically.
  • gji doesn't move uncommitted changes when you navigate. new --take is an explicit operation for doing that.
  • Cleanup can delete branches and uncommitted files. Undo restores recorded Git/worktree state, not those uncommitted files.

If those tradeoffs fit, follow the quick start. Its first success is returning to the work you left open, not learning a long list of commands.