Menu · Troubleshooting and FAQ

Troubleshooting and FAQ

Claude did the action and paws didn't stop it

Run unbound-paws explain with the exact command from the same folder. If your rule has no →, it doesn't match. Check the regex, the event and any ! lines. If it matches but a real session allows the call, the skill was already loaded. If nothing happens at all, check the hook is registered. The paws command should appear in .claude/settings.json or ~/.claude/settings.json, and Claude Code needs a restart after init.

unbound-paws: command not found

The installer put it in ~/.local/bin and added that folder to your shell's startup file. Open a new terminal, or run export PATH="$HOME/.local/bin:$PATH". If Claude Code shows a hook error saying the same, start it from a terminal where unbound-paws version works.

paws keeps denying after the skill loaded

Check the rule's skill is exactly the skill's name:, and the skill is installed where Claude Code can load it. A rule for a skill that isn't installed denies every time.

Isn't an LLM following instructions just a suggestion?

Yes, and paws doesn't claim otherwise. It guarantees the skill was loaded before the action, every time. What Claude does with it is up to the skill.

How is this different from a rules file?

A rules file loads text when Claude touches certain files. paws fires on actions, such as commits, PRs, MCP sends, session start and repo conditions, before the first write. It also installs and pins the skill for you.

Does it cost anything?

The hook, the rule format and the catalog are free and open source, and the hook never needs the portal. The portal is free too. Pro keeps 90 days of history instead of 30.