Troubleshooting

macOS: binary blocked by Gatekeeper

If macOS shows a “cannot be opened” or “unverified developer” error after installation, clear the quarantine attributes and ad-hoc sign the binary. Run this once:

sudo xattr -cr /usr/local/bin/hiauditagent
sudo codesign --force --sign - /usr/local/bin/hiauditagent

I lost my API key

The full API key value is displayed only at creation time. If you lose it, create a new key from the API Keys page in the dashboard, then re-run the installer with the new key.

HiAUDIT isn’t showing up in my editor

• Make sure you ran hiauditagent mcp add after installing.
• Restart your editor — MCP servers are only discovered on startup.
• Confirm the binary is on your PATH by running hiauditagent --help.

Where are the MCP config files?

hiauditagent mcp add writes to your editor’s MCP config file:

You can open these files to confirm the hiauditagent server entry was added, or to configure it manually (see Connect to your IDE).

Verifying the install

Run hiauditagent --help. If the help text prints, the agent is installed correctly. If the command is not found, the binary may not be on your PATH — re-run the installer.