Skip to main content
This guide covers common Roo Code integration errors. For initial setup, see the Roo Code Integration guide.

​
Prerequisites Reminder

  • An Unbound account with an API key
  • The Roo Code extension installed in your IDE
Run unbound setup roo-code and the CLI prints the two values Roo Code asks for — the API provider to pick, and your API key.

​
”Invalid API Key” Error

​
”I can’t find the unbound provider”

Run unbound setup roo-code. It prints the two values Roo Code asks for: the API provider to select, and your API key. If unbound is still not in Roo Code’s API Provider list, update the extension to its latest version, restart VS Code, and open the list again. Then configure it using the Roo Code Integration guide.

​
Connection Errors

1

Check internet connection

Ensure you can reach api.getunbound.ai.
2

Configure corporate proxy

If behind a corporate proxy, configure proxy settings in VS Code: File → Preferences → Settings → search “proxy”.
3

Handle SSL certificate errors

If behind corporate SSL inspection, set:

​
Credits Exhausted (Not an API Key Issue)

If you get a 402 error, your API key is valid but your credits are used up. See Credits & Budget for resolution steps.

​
Verifying the Connection

After setup, send a simple test message in Roo Code. If you get a response from the AI, the integration is working correctly. If you see an error, check the Roo Code output panel for detailed logs:
1

Open the output panel

Go to View → Output in VS Code.
2

Select Roo Code

Select Roo Code from the dropdown.
3

Look for error details

Check the logs for specific error messages.

​
Still Having Issues?

Roo Code Setup Guide

Full Roo Code integration guide

API Key Troubleshooting

Fix invalid API key errors