Forge & Code
Troubleshooting
The problems we see most often, with what causes them and how to fix them.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The browser does not open at sign-in | No default browser, or a remote or headless session. | Run rodium login --with-account --no-browser: the sign-in URL is printed, open it in your browser. |
| The app asks you to sign in again | The saved sign-in expired or the model list could not be loaded for your account. | Sign out and sign in again with rodium logout then rodium login, or /logout and /login in a session. |
| An API key is refused | The key is mistyped, revoked, or not a RodiumAi key. | RodiumAi keys start with rd_sk_. Check or create one in API keys. The key is checked against the gateway before it is saved. |
| No FRODI left | The current allowance is used up. | Check the date of the next reset on your Forge & Code overview, or use Change plan. See RODI and FRODI credits. |
| I paid but my plan does not show | The payment confirmation is still on its way. | The overview keeps checking for a minute or two after you come back. If it is still pending, click Check again, and contact support if it stays that way. |
rodium is not found after install | The npm global folder is not in your PATH, or Node.js is older than 22. | Check node --version, then add the folder printed by npm prefix -g (its bin folder on macOS and Linux) to your PATH. |
| The agent seems stuck | A stale background process. | CLI: run rodium doctor, then rodium doctor fix. Extension: RodiumAi: Restart Backend and RodiumAi: Show Logs. |
gh or another tool is not found in the desktop app | The app was launched from the Dock or Finder with a minimal PATH. | RodiumAi imports your login shell PATH at startup. Make sure the tool works in a new terminal, then restart the app. |
Proxies and certificates
The CLI trusts your operating system's certificate store, so it works behind TLS-inspecting proxies and with internal certificates. On launch, the rodium wrapper writes the system trust anchors to ~/.rodiumai/cli-node-extra-ca-certs.pem and points NODE_EXTRA_CA_CERTS at it. Certificates you set in NODE_EXTRA_CA_CERTS yourself are merged in.
Run with RODIUMAI_DEBUG=1 to see which certificates were loaded and which paths are used.
Diagnostics and logs
…RODIUMAI_LOG_LEVEL=debugmakes the log more detailed, andRODIUMAI_LOG_PATHchooses where it is written.- In the editor extension, RodiumAi: Show Logs opens the backend output.
rodium statusshows the connection, the account, the FRODI left and the default model.
Still stuck?
Open a ticket from the Support page of your dashboard and include the output of rodium status and rodium doctor, with the time of the problem.