install openclaude

One npm command on macOS, Linux, or Windows. An AUR package exists for Arch.

requirements

  • Node.js 22 or newer — grab it from nodejs.org and confirm with node --version.
  • A terminal: Terminal/iTerm on macOS, any shell on Linux, PowerShell or Windows Terminal on Windows.
  • ripgrep is bundled; if startup reports ripgrep not found, install it system-wide and confirm rg --version works.

install with npm

npm install -g @twigpine/openclaude@latest

This installs the openclaude binary globally. On macOS/Linux you may need a Node installation that doesn't require sudo for global installs (nvm, fnm, or Homebrew node all work).

upgrading from @gitlawb/openclaude

The package moved to the @twigpine scope and the old one is no longer updated. Both packages provide the openclaude command, so npm refuses to install one over the other. Remove the old package first: 

npm uninstall -g @gitlawb/openclaude
npm install -g @twigpine/openclaude@latest

Your settings and sessions (~/.openclaude and ~/.openclaude.json) are not touched. Don't use --force to install over the old package instead: a later uninstall of the old one would then remove the openclaude command. If that happens, uninstall @twigpine/openclaude and install it again.

arch linux (aur)

A community-maintained AUR package is available: 

paru -S openclaude

verify the install

openclaude --version

To check which version is the latest published release: 

npm view @twigpine/openclaude dist-tags

update

Re-run the install command — @latest always resolves to the newest release:

npm install -g @twigpine/openclaude@latest

troubleshooting

  • Old version after update — your shell may cache the binary path; run hash -r (bash/zsh) or open a new terminal.
  • Multiple Node versions — global installs are per Node version with nvm/fnm; make sure you installed under the version your shell uses.
  • Anything else — run /doctor inside openclaude to diagnose the installation, or check the issue tracker.

Next: run your first session →