”No api_key found in callback. Exiting.”
The authentication flow didn’t complete properly. How to fix:1
Run the setup command again
Re-run the Unbound CLI setup for Claude Code.
2
Complete the browser step fully
Don’t close the browser tab early. Wait for the success page.
3
Check pop-up blockers
Ensure pop-ups are not blocked in your browser.
4
Try a different browser
Some SSO providers have issues with specific browsers.
5
Use manual setup as fallback
If the issue persists, set environment variables manually:
“API Key Verification Failed” / “Fetch Failed”
This usually indicates a network or configuration issue. Common causes and fixes:- Check your network connection — ensure you can reach
api.getunbound.ai - Corporate proxy — if behind a corporate proxy, configure proxy settings in your terminal
- Verify environment variables are set correctly:
Both should return values. If empty, your shell profile didn’t load them — re-add them and run
source ~/.zshrc.
”Self-Signed Certificate Detected”
This occurs when your corporate network uses SSL inspection or interception. Fix: Add your corporate CA certificate to Node.js:~/.bashrc, ~/.zshrc, or PowerShell profile). Contact your IT team for the correct certificate file path.
”Claude Code Not Found” After Installation
1
Check your PATH
Verify npm global bin is in your PATH:
2
Add to PATH if missing
Add the npm global bin directory to your PATH in your shell profile.
3
Avoid sudo with npm
If you installed with
sudo, uninstall and reinstall using:4
Restart your terminal
After updating your PATH, restart your terminal completely.
Node.js/npm Version Issues
If you updated Node.js or npm and Claude Code stopped working:- Reinstall Claude Code:
- Verify the installation:
- If using
nvm, make sure the correct Node.js version is active