Skip to main content
This guide covers common errors when using Claude Code CLI through Novageness. For initial setup, see the Claude Code Integration guide.

​
”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 Novageness 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:

​
TypeError: fetch failed / “API Key Verification Failed”

This usually indicates a network or configuration issue. Common causes and fixes:
  • Check your network connection — ensure you can reach api.novageness.com
  • 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_CERT_IN_CHAIN / “Self-Signed Certificate Detected” / unable to get local issuer certificate

This occurs when your corporate network uses SSL inspection or interception. Fix: Add your corporate CA certificate to Node.js:
Add this to your shell profile (~/.bashrc, ~/.zshrc, or PowerShell profile). Contact your IT team for the correct certificate file path.

​
apiKeyHelper did not return a valid value

Claude Code asked Novageness’s key helper for your API key and got nothing back. The helper reads the NOVAGENESS_API_KEY environment variable, so this almost always means Claude Code is running somewhere that variable was never loaded. Check it first:
  • Unset, in a terminal you opened before setup ran — open a brand-new terminal and start Claude Code from it. Environment variables load when the shell starts; an already-open terminal never sees them.
  • Set in your terminal, but Claude Code still fails — you’re launching Claude Code from the Dock, Spotlight or an IDE, none of which read your shell profile. Launch it from a terminal, or have your IDE inherit the shell environment.
  • Unset everywhere — the variable was removed while the key helper stayed configured. Re-run your Claude Code setup.
After any fix, fully quit Claude Code and relaunch it from a new terminal — it reads this configuration only at startup. On an MDM-managed device, ask your administrator to re-run the MDM deployment rather than fixing it by hand; that restores both halves together.

​
”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:
  1. Reinstall Claude Code:
  2. Verify the installation:
  3. If using nvm, make sure the correct Node.js version is active

​
Token Limit Exceeded Errors

If you see “Claude’s response exceeded the output token maximum”, set the environment variable to increase the limit:
Add to your shell profile and restart your terminal.

​
Still Having Issues?

See API Key Troubleshooting for invalid key and authentication errors.