Who it is forA developer who uses Codex CLI, Claude Code or Cursor and wants all of them to route through the same OmniRoute server.
The problemEach coding tool needs its own configuration to reach OmniRoute, and setting them up one by one takes time.
The outcomeProfiles or tool-native config for the chosen coding tool point at your OmniRoute server.
What you need first
- VS Code 1.104 or later, or a VS Code fork such as Cursor, Windsurf or VSCodium
- Node.js with npm, to install the OmniRoute CLI
- A running OmniRoute server, local or remote, with at least one provider configured or the built-in free ones
Steps
- Make sure the
omnirouteCLI is installed and reachable at the path set inomnicopilot.cliPath. - Run the command
OmniRoute: Configure Coding CLIfrom the VS Code command palette. - Pick the tool, such as Codex CLI or Claude Code, and let the extension generate the profile.
- Launch the tool with its profile, for example
codex --profile glm52for Codex CLI oromniroute launch --profilefor Claude Code.
Prompt for your agent
Using the diegosouzapw/OmniCopilot README, run the Configure Coding CLI flow for <tool-name> on this machine. Report the profile file or launch command it produced. Verify that the generated profile points to the OmniRoute server URL in omnicopilot.baseUrl.
Caveat. The README says the extension drives the omniroute CLI, so that CLI must be installed and working before this command produces anything.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for diegosouzapw/OmniCopilot and "Configure Codex, Claude Code and Cursor for OmniRoute"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer