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 Unbound-modified version of Roo Code (not the standard VS Code marketplace version)
The standard Roo Code from the VS Code marketplace does NOT include the “unbound” provider option. You must use the Unbound-modified version.

​
”Invalid API Key” Error

​
”Has Roo Code Discontinued Unbound as a Provider?”

No. If you don’t see the “unbound” provider option in the dropdown, you’re using the standard marketplace version of Roo Code. You need the Unbound-modified version. How to fix:
  1. Uninstall the standard Roo Code extension from VS Code
  2. Contact your admin for the correct installation link for the Unbound-modified version
  3. Install the Unbound version
  4. Restart VS Code and configure 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 to help diagnose the issue.

​
Still Having Issues?

Roo Code Setup Guide

Full Roo Code integration guide

API Key Troubleshooting

Fix invalid API key errors