Roo Code Agent setup

Roo Code is an editor coding Agent for VS Code and JetBrains. It can inspect and change a workspace, run commands, and switch between task-specific modes. Its OpenAI Compatible provider can connect directly to Lumoswitch.

Create a Lumoswitch API configuration with OpenAI-compatible output first. Use a model with native tool calling: Roo depends on structured tools for file edits and terminal actions.

Choose a setup method

Method	Available?	Notes
One-time launch	No	The editor extension owns provider state and encrypted credentials
Persistent use	Yes	Save a named API configuration profile in Roo
Removal	Yes	Delete only the Lumoswitch profile and its stored credential
Settings import	Optional	Roo can import profiles, but exported files contain API Keys in plain text

Lumoswitch does not publish an automatic terminal import for Roo. The current Roo CLI provider list does not expose a generic custom OpenAI-compatible endpoint, while the editor extension stores credentials through editor SecretStorage.

Prepare the connection values

Placeholder	Value
`{{api_base_url}}`	The downstream API URL, including `/v1`
`{{access_key}}`	The Lumoswitch Access Key selected for this configuration
`{{model}}`	The client-facing model name shown by the API configuration

Configure a Roo profile

Install and open the official Roo Code extension in VS Code or JetBrains.
Open Roo settings and create a new API Configuration Profile named Lumoswitch.
Select OpenAI Compatible as the API Provider.
Enter {{api_base_url}} as the Base URL, {{access_key}} as the API Key, and {{model}} as the Model.
Enter the model's real context window and maximum output size instead of assuming the upstream defaults.
Save the profile, select it in Roo, and test a small read-only request before allowing edits or terminal commands.

Keep native tool calling enabled. If the selected model cannot reliably call tools, use a different Lumoswitch configuration rather than treating successful chat as a complete Agent test.

Reuse settings deliberately

Roo's native Export Settings and Import Settings actions are the supported way to move profiles between editors or machines. Exported settings include API Keys in plain text, so:

save the export only in a private location;
never commit it to a repository or attach it to an issue;
delete the transfer file after importing and verifying the profile.

Teams that already maintain a protected Roo settings export can point VS Code setting roo-cline.autoImportSettingsPath at it. Do this only when the file lifecycle and access controls are understood; it is not enabled by this guide.

Remove the setup

Open Roo's API Configuration Profiles.
Select Lumoswitch and use the profile delete action.
If Roo still shows the old secret, clear the profile credential through the same provider UI and reload the editor.
Delete any temporary settings-export file that contains the Access Key.

Do not delete the entire Roo extension data directory. It can contain task history, modes, rules, and unrelated providers, while editor SecretStorage may be managed separately.

Verify and troubleshoot

A 401 means the saved profile Key is missing, stale, or attached to a different profile.
For 404, check for a duplicated /v1 and confirm the client-facing model name.
If requests succeed but tools fail, verify the model supports native tool calling and that the Lumoswitch output protocol is OpenAI-compatible.
Keep context and output limits accurate; inflated values can make Roo build requests the selected model cannot accept.

References: Roo OpenAI Compatible provider, settings management, and API configuration profiles. Last verified: 2026-08-23.

Maintainer publication fields

Platform ID: roo-code
Display name: Roo Code
Downstream protocol: openai-compatible
Temporary publication: disabled; Roo's editor extension owns provider state and credentials
Persistent publication: disabled; native profiles and SecretStorage are safer than rewriting editor state
Display order: 89
Last verified: 2026-08-23