Skip to main content

Troubleshooting

Start with /bianoble-status. It answers most of what follows in one screen, and several of the problems below look identical until you read it.

Catalog: 0 tools visible​

The most likely first-run failure, and it is a precondition rather than a warning. Your session is authenticated correctly, and the organization it is bound to has no tools in its catalog — so every tool call will fail with not found in catalog.

Nothing on your machine fixes this. Either:

  • the organization genuinely has nothing entitled yet — contact support@noblecloak.com; or
  • you are bound to the wrong organization — see below.

Reinstalling the plugin does not change either.

Wrong organization​

/bianoble-status labels its organization line "hooks token" for a reason: there are two credentials, and it can only see one of them.

  • /bianoble-login mints the governance session the hooks use.
  • Claude Code's native OAuth mints a separate token for the MCP server.

Both bind whichever organization was your default at the moment they were issued — and they are issued at different moments. If your default organization changed in between, they can disagree: local governance checks run against one organization while your tool calls resolve against the other. There is no way to read the second token from your side, so this cannot be detected locally; it shows up as tools missing or resolving oddly.

The fix is both halves, in order. Set your intended default organization, then:

  1. Run /bianoble-login again.
  2. Reconnect the bianoble server from /mcp, or restart Claude Code.

Doing only one leaves the mismatch exactly as it was.

Not connected or Token expired​

Run /bianoble-login. If you were signed in recently this is usually a single click.

Sessions refresh automatically at session start when they are near expiry. A session left idle long enough will still lapse, which is expected.

/bianoble-connect printed nothing​

That is success. The command refreshes the governance session token only when it is at or near expiry. If your token is still good it exits silently with nothing to do.

Two things it deliberately does not do:

  • It does not check with the server whether your token is still accepted — it reads local expiry only. A token that is locally valid but rejected server side will not be caught here; /bianoble-status, which probes the catalog live, will.
  • It does not touch the MCP connection or rewrite any MCP configuration.

After an entitlement change, /bianoble-connect is not the command you want. New entitlements apply server-side on your next tool call — there is no local configuration to refresh. If tools still do not appear, reconnect the bianoble server from /mcp or restart Claude Code.

A tool call was refused​

Check your mode first — /bianoble-status prints it.

  • In audit-only (the default), the plugin blocks nothing, including a server deny. If a local call did not run, the plugin is not why.
  • In enforce mode, a refusal is your organization's policy working. Retrying will not change it; a policy or entitlement change will.

Refusals of NobleCloak tools are a separate path — those are governed at our gateway, and the connector troubleshooting page explains how to read them in the Execution Ledger.

Nothing appears to be governed at all​

Most likely nothing is wrong. Audit-only is the default: calls are checked and recorded, and they all run. Confirm with /bianoble-status before treating silence as a fault.

If you expected enforcement, it is enabled deliberately by your organization rather than by the plugin defaulting to it.

Commands are missing after installing​

The plugin's commands and hooks load at startup. Restart Claude Code. If /bianoble-status still does not exist, the plugin did not install — revisit the install guide.

Still stuck​

Contact support@noblecloak.com and include the output of /bianoble-status. It identifies the cause of most of the above immediately.