Agents and developer clients
Choose the client protocol before connecting Codex, Claude Code, or Cursor to XiuRouter
Choose your client, configure the matching Base URL and API key, then confirm the connection with one real task.
Choose the client you use
Each client uses a different API format and setup location. Choose one to see the correct path.
- Use for
- Local Codex work in the CLI, IDE extension, or desktop app.
- How to connect
- Choose Responses, configure a XiuRouter provider for new local tasks, and verify it with one small read-only task.
- Before you rely on it
- The configuration applies to local Codex tasks. Cloud ChatGPT, hosted retrieval, stored conversations, and background mode continue to use their own services.
- Use for
- Claude Code CLI, the VS Code extension, and the desktop Code interface.
- How to connect
- Choose Anthropic Messages and use the gateway root without duplicating /v1. Confirm success only after a local task completes.
- Before you rely on it
- The Messages endpoint handles model requests. Claude cloud environments, SSH, Remote Control, and hosted server tools remain Anthropic services.
- Use for
- Cursor custom models when the OpenAI Base URL can be changed.
- How to connect
- Choose Chat Completions and verify Ask plus the request record first. Test model-specific tool calling separately before relying on Agent edits.
- Before you rely on it
- The custom Base URL affects the matching model requests. Cursor-specific models, Tab completion, and file-edit behavior still depend on Cursor and the selected model.
Confirm the setup with one real task
Test the smallest real task you depend on, then check its Usage record.
- 1
Confirm the client can reach the expected protocol path with the selected model.
- 2
For coding agents, test one bounded tool or file task instead of only a text reply.
- 3
Check Usage for the model, tier, status, tokens, and recorded cost before relying on the setup.