Update and uninstall
Update or uninstall Sheriff for Claude Code and Codex. Manage project-local and global installations and keep your test workflows up to date.
Upgrading to 0.2.0
Sheriff 0.2.0 adds automatic local dependency installation and a keyboard-driven terminal wizard. Run npx @dagim_codes/sheriff@latest to choose your tools and scope with ↑/↓ and Enter. Local setup uses npm, pnpm, Yarn, or Bun according to the project, fixing the failure caused by running npm against a pnpm dependency tree.
The wizard includes a gold selection highlight, one question per screen, a version bar, project context, and responsive Western terminal artwork. It restores the terminal after confirmation or cancellation. Explicit flags remain available for automation.
Package-backed runtimes and Codex's six action skills from 0.1.6 are retained. Existing dependencies are not automatically upgraded or moved between dependency sections. Use the commands below to upgrade an existing installation, or replace @latest with @0.2.0 to pin this release.
Update inside your AI tool
Use /sheriff:update or $sheriff update to retain the installation's tool and scope. There is no separate $sheriff-update skill. Local updates update the project dependency and refresh adapters; global updates refresh the copied runtime.
Update a project installation
Update the dependency with the project's existing package manager, then refresh the integrations you use:
npm install --save-dev @dagim_codes/sheriff@latest
npx @dagim_codes/sheriff@latestpnpm add -D @dagim_codes/sheriff@latest
npx @dagim_codes/sheriff@latestyarn add --dev @dagim_codes/sheriff@latest
npx @dagim_codes/sheriff@latestbun add --dev @dagim_codes/sheriff@latest
npx @dagim_codes/sheriff@latestChoose your existing AI tool and This project (local) in the wizard. Both hosts share the dependency, so updating it updates both runtimes. Refresh both integrations when both are installed. Preserve an existing production dependency in dependencies rather than moving it to devDependencies.
Older copied project installations migrate their owned files to small adapters. Existing single-entry Codex installations gain the six action skills. Unrelated files and settings, tests, and .sheriff/ state are preserved; conflicting unowned files cause the installer to stop.
Restart your AI tool after adding new commands or skills.
Remove project integrations
Remove the adapters before removing the dependency:
npx @dagim_codes/sheriff@latest --uninstall
npm uninstall --save-dev @dagim_codes/sheriffnpx @dagim_codes/sheriff@latest --uninstall
pnpm remove @dagim_codes/sheriffChoose the integration to remove and This project (local) in the uninstall wizard. Keep the dependency until every integration using it has been removed. Integration removal does not edit the package declaration itself.
If node_modules is already missing, use:
npx @dagim_codes/sheriff@latest --uninstallPersonal installation
Choose your AI tool and All your projects (global) in either wizard.
npx @dagim_codes/sheriff@latestnpx @dagim_codes/sheriff@latest --uninstallWhat is preserved
Updates and uninstall preserve generated tests, project .sheriff/ state, and unrelated files and settings. Removal deletes owned adapters and Codex action skills, preserving personal resources inside their directories. Normal installation write failures roll back changes; abrupt process or machine termination is not a transactional filesystem guarantee.