Skip to main content
ValarCode connects your coding tools to Valar, with model selection, routing controls, and usage attributed to each engineer. It supports Claude Code, Claude Desktop, Cursor, Codex, Pi, Oh My Pi, opencode, and VS Code through Copilot Chat. On macOS and Windows 11, Claude Code and Claude Desktop can use a shared on-device proxy while keeping their Claude login; on macOS, Cursor can use it too. Direct integrations configure the tool to use the Valar endpoint. You control routing with your coding key and review usage and savings in the dashboard.

​
Why teams use it

  • Choose frontier and open models from supported coding tools.
  • Manage model routing without changing each engineer’s setup for every policy change.
  • Use eligible Claude subscription allowance first through the optional on-device proxy.
  • Track usage and savings per engineer.

​
How it works

  1. Configure a coding key with the Valar CLI.
  2. Connect each harness. Claude Code and Desktop can use the shared proxy or direct routing; other harnesses use their own integrations.
  3. Choose models in the harness. Your key’s policy controls requests served through Valar. With quota-first enabled on the proxy, eligible Claude requests can use your subscription instead.
  4. Review Valar-served usage and savings in the dashboard.
See Model routing for routing controls and On-device proxy for shared setup and subscription-first routing. To deploy with MDM, see Roll out with MDM.

​
Get started

Set up ValarCode

Install the CLI, create a coding key, and connect a harness.

Model routing

Choose how your coding key routes model requests.

On-device proxy

Shared proxy setup and lifecycle.

Models

The open-weight targets and the frontier Claude tiers.

Analytics & savings

Per-engineer usage and how savings are worked out.

​
Supported harnesses

Each harness has its own page covering how to connect it and what the CLI writes behind the scenes:

Claude Code

valar claude on

Claude Desktop

valar claude-desktop on

Cursor

valar cursor on

Codex

valar codex on

opencode

valar opencode on

Pi

valar pi on

Oh My Pi

valar ohmypi on

VS Code

valar copilot on

​
LiteLLM

If you run a LiteLLM proxy, you can keep it and still use ValarCode. Claude Code (or Pi) points at LiteLLM, which forwards requests to Valar. For per-engineer routing and attribution, LiteLLM must preserve the client ID header when forwarding requests.

LiteLLM integration

Route Claude Code through a LiteLLM proxy without losing per-engineer attribution.