Integrations
Clients that cannot use RouteMux
Tools where pointing at a third-party endpoint is impossible or no longer maintained, so you stop looking for a setting that is not there.
Some tools cannot be pointed at RouteMux — or at any other gateway. That is a property of the tool, not of your configuration, and it is worth knowing before you spend an evening looking for a base URL field. This page is deliberately short: it lists only cases we have checked.
Discontinued or archived
Their repositories are archived, so no configuration will be added.
| Tool | State | Use instead |
|---|---|---|
| Roo Code | Repository archived, last commit 2026-05-15 | Kilo Code — active, and it exposes all three protocol modes |
| Void | Repository archived, last commit 2026-06-02 | Any of the supported editors |
| Flowise | Repository archived, last commit 2026-08-13 | Dify, which we have a guide for |
| Plandex | Not archived, but no commits since 2025-10-03 | — |
Officially closed as won't-fix
- VS Code's Copilot BYOK, for a custom Anthropic base URL. Tracked as
microsoft/vscode#286734, "Support custom base URL for BYOK Anthropic API", closed on 2026-01-09 with thewont-fixlabel. Bring-your-own-key works against the vendors VS Code knows about; it will not accept an arbitrary endpoint for the Anthropic protocol.
Headless and CLI agents that route through their vendor
- Cursor's CLI and background agents. The
Override OpenAI Base URLsetting in the IDE is a chat feature. Support for headless agents is an open feature request, not a setting you have overlooked. The IDE itself is partially usable — see the Cursor page for what does and does not work.
How to tell in thirty seconds, for anything not listed here
Open the tool's model or provider settings and look for a free-text field for a URL. Then:
- A URL field you can type into → it will almost certainly work. Pick the protocol from the compatibility matrix and go.
- Only a key field, next to a fixed list of vendor names → there is no way in. The tool resolves the endpoint itself from whichever vendor you picked, and a key from us will be sent to that vendor, not to us. A "custom model" option that still makes you choose from a menu of suppliers is this case, not the one above.
- A key field plus a separate "path" or "endpoint" box → it will work, but the two fields
split the URL between them. Check which half expects
/v1.
If a tool moves from the second category to the first, we would like to know — a guide is usually a short afternoon's work once the field exists.