Uninstall the old thing CLI. Install the latest one.

Updated August 31, 2026

The CLI now lives in the standalone thing-cli repository. The npm package is still @unravel-tech/thing and the command is still thing. Replace an older global copy with the latest release in a couple of minutes.

1. Find every installed thing binary
2. Replace the package with the same installer
3. Refresh your shell and verify the version

Replace a global installation

Use the column for the package manager that originally installed thing. Both flows remove only the executable package, then install the current release from npm.

$ npm uninstall --global @unravel-tech/thing
$ npm install --global @unravel-tech/thing@latest

$ bun remove --global @unravel-tech/thing
$ bun install --global @unravel-tech/thing@latest

Using npx or bunx instead?

There is no global package to uninstall. Include @latest in the one-off command to bypass an older cached release:

Verify what your shell will run

Open a new terminal, or run hash -r in Bash or Zsh, then check the resolved binary and its version. PowerShell users can replace type -a thing with Get-Command thing -All.

$ type -a thing
thing is /usr/local/bin/thing
$ thing --version
thing 0.7.0

If the old version still appears

1. Look for duplicates. type -a thing lists every matching binary in shell search order. More than one result usually means npm and Bun both installed a copy.
2. Uninstall through its package manager. Run the matching uninstall command above for each managed copy. Avoid deleting a resolved binary by hand; its package manager should remove the link it owns.
3. Refresh the command cache. Open a new terminal or run hash -r, then repeat type -a thing and thing --version.

After the upgrade

Your existing login should work immediately. Run thing whoami to confirm it. The current CLI can also keep several named logins: use thing login --account work, inspect them with thing accounts, and bind a repository with thing switch work --local.