> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getunbound.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Roo Code Integration Troubleshooting

> Fix common Roo Code errors including invalid API key, missing unbound provider, and connection issues

This guide covers common Roo Code integration errors. For initial setup, see the [Roo Code Integration guide](/integrations/roo-code-integration).

## Prerequisites Reminder

* An Unbound account with an API key
* The **Unbound-modified version of Roo Code** (not the standard VS Code marketplace version)

<Warning>
  The standard Roo Code from the VS Code marketplace does **NOT** include the "unbound" provider option. You must use the Unbound-modified version.
</Warning>

## "Invalid API Key" Error

| Check              | Fix                                                                                |
| ------------------ | ---------------------------------------------------------------------------------- |
| Wrong API provider | Ensure you selected **"unbound"** as the API provider, not "OpenAI" or "Anthropic" |
| Stale key          | Copy the API key fresh from **Connect → AI Coding Tools → Roo Code**               |
| Extra spaces       | Check there are no extra spaces in the key                                         |
| Cached session     | Restart VS Code after changing settings                                            |
| Wrong version      | Verify you're using the **Unbound-modified** Roo Code, not the marketplace version |

## "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](/integrations/roo-code-integration)

## Connection Errors

<Steps>
  <Step title="Check internet connection">
    Ensure you can reach `api.getunbound.ai`.
  </Step>

  <Step title="Configure corporate proxy">
    If behind a corporate proxy, configure proxy settings in VS Code: File → Preferences → Settings → search "proxy".
  </Step>

  <Step title="Handle SSL certificate errors">
    If behind corporate SSL inspection, set:

    ```bash theme={null}
    export NODE_EXTRA_CA_CERTS="/path/to/your/corporate-ca.pem"
    ```
  </Step>
</Steps>

## 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](/support/billing/credits-usage-and-budgets) 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:

<Steps>
  <Step title="Open the output panel">
    Go to **View → Output** in VS Code.
  </Step>

  <Step title="Select Roo Code">
    Select **Roo Code** from the dropdown.
  </Step>

  <Step title="Look for error details">
    Check the logs for specific error messages to help diagnose the issue.
  </Step>
</Steps>

## Still Having Issues?

<CardGroup cols={2}>
  <Card title="Roo Code Setup Guide" icon="book" href="/integrations/roo-code-integration">
    Full Roo Code integration guide
  </Card>

  <Card title="API Key Troubleshooting" icon="key" href="/support/api-keys/troubleshooting-api-keys">
    Fix invalid API key errors
  </Card>
</CardGroup>