Menu · Installation

Installation

There are builds for macOS and Linux on x64 and arm64, and for Windows through npm. Only Claude Code is supported right now.

curl -fsSL https://paws.getunbound.ai/install.sh | bashunbound-paws init                      # turn it on for this project

The script downloads the release for your OS and chip from GitHub, checks it against the release's checksums.txt and installs it as ~/.local/bin/unbound-paws, the folder Claude Code's own installer uses. If that folder isn't on your PATH, it adds it to ~/.zshrc or ~/.bashrc; open a new terminal afterwards. It doesn't need sudo, refuses to run under it, and changes no Claude settings. With npm, npm i -g unbound-paws gives you the same unbound-paws command; on macOS and Linux the install swaps npm's Node launcher for the binary, so it's just as fast. On Windows, use npm for now.

With npm instead
npm i -g unbound-paws

What init does

  • It adds four hooks to a Claude Code settings.json. PreToolUse and SessionStart decide. PostToolUse and Stop run in the background, without Claude Code waiting, to write the local log and sync with the portal if you logged in. Each runs unbound-paws gate, which works on every teammate's machine. Hooks you already have stay as they are.
  • The hook runs before every tool call, and unbound-paws is the native binary, so each call costs a few milliseconds and never touches npm. A project and --global get the same line, so Claude Code runs it once even when both are set. If unbound-paws isn't on your PATH when you run init (from npx or a source build), init copies the binary to ~/.paws/bin and writes "$HOME/.paws/bin/paws" gate instead.
  • It installs no skills. The paws skill, which helps Claude write rules, is a separate step: unbound-paws skill.
  • The hints paws prints name unbound-paws commands. login also tells you when paws isn't registered in ~/.claude/settings.json, because skills from the portal install for every project.
.claude/settings.json (excerpt)
{  "hooks": {    "PreToolUse": [{ "hooks": [{ "type": "command", "command": "unbound-paws gate" }] }],    ...  }}

This project or every project

CommandWritesApplies to
unbound-paws init<repo>/.claude/settings.jsonThe git repository you're in. Outside a repository, the current folder.
unbound-paws init --global~/.claude/settings.jsonEvery project you open in Claude Code. $CLAUDE_CONFIG_DIR replaces ~/.claude when set.
unbound-paws init --settings <path><path>A file you name, such as .claude/settings.local.json to keep paws out of a shared file.

A project install lives in a file you can commit, so the team gets paws when they pull. Review changes to .claude/settings.json like code. It decides what runs on every tool call.

Upgrade

curl -fsSL https://paws.getunbound.ai/install.sh | bashnpm i -g unbound-paws@latest        # if you installed with npm

Run the install line again, or npm i -g unbound-paws@latest if you installed with npm. Every project's hook runs that same unbound-paws, so the next tool call uses the new version. If you use the paws skill, run unbound-paws skill after upgrading so it matches.

Uninstall

Turn paws off for this project, or for every project:

unbound-paws uninstall
unbound-paws uninstall --global

uninstall removes the hook entries paws added and the paws skill next to that settings file, if paws installed it and you haven't edited it. Your other settings and hooks stay. A settings file left empty is deleted, and so are empty .claude/skills and .claude folders.

To remove paws completely, also delete the program (or run npm rm -g unbound-paws) and, if you don't want to keep them, your rules, packs, audit log and login:

rm ~/.local/bin/unbound-paws
rm -rf ~/.paws

From source

git clone https://github.com/websentry-ai/paws && cd pawsgo build -o ~/.local/bin/unbound-paws ./cmd/paws && unbound-paws init