Troubleshooting

Node.js version too old

Sensitive Canary requires Node.js 22.6.0 or later for --experimental-strip-types.

node --version

Install or update from nodejs.org.

Hooks not running after install

1. Restart Claude Code — a session that was already running when the plugin was installed does not pick the hooks up. /plugin lists it as enabled either way, so the state that checks nothing looks exactly like the state that works. Restart first, then check anything else.
2. Check plugin status — run /plugin and verify sensitive-canary is listed and enabled.
3. Check hooks config — for manual installs, verify the hooks entries exist in ~/.claude/settings.json

False positives

If legitimate content is being blocked:

• Add [allow-secret], [allow-pii], or [allow-all] to your prompt to bypass the check for that message
• Allow tags apply only to the current message and do not persist
• For PreToolUse hooks a tag stops applying once a tool result is recorded after it. Tool calls issued together, before any result comes back, are all covered by one tag — a tag is not a promise that only the next one goes through

.env file blocking

This is by design. .env and its siblings are blocked by filename, but only while the secret category is enabled (the default). Template names (.env.example, .env.sample, .env.template, .env.dist, .env.defaults) are exempt from the name guard and scanned on their contents instead, so an ordinary template reads fine and one holding a live key does not. [allow-secret] or [allow-all] will lift this block if you need Claude to read an .env file intentionally. [allow-pii] will not: the block is a secret guard.

Plugin not found after marketplace registration

Verify the marketplace was registered correctly:

1. Run /plugin and check the Marketplaces tab
2. Ensure coo-quack/claude-code-marketplace appears in the list
3. Try running /plugin install sensitive-canary@coo-quack again

Still stuck?

Open an issue on GitHub.