Choose a routing method
valar claude-desktop on selects the proxy lane when the proxy is provisioned; otherwise it uses the direct lane. Pass --direct to explicitly choose the provider profile.
On-device proxy
Provision the shared component once, then enable Desktop:valar claude-desktop on and off do what valar claude on and off do, and print the same output. Both end with a line that says what happened to Desktop:
valar proxy enable --ingress pac.
On this lane, valar claude-desktop on also adds CLAUDE_CODE_AUTO_MODE_SERVER=0 to the env block of ~/.claude/settings.json when that key is absent. Desktop’s local Code sessions read that file whatever else is configured, and the value keeps auto mode on client-side review, so a routed Code session does not ask for server-side review or show the classifier-billing notice. valar claude-desktop off removes the key again, unless you set the value yourself. Chat and Cowork settings are not touched.
Direct lane
--with-chat on each on that should include Chat. The direct profile has its own chat history; it does not merge with your claude.ai history when you switch lanes.
Switch lanes and running sessions
You can switch directly between lanes:- No: routing and the running app remain unchanged.
- Yes: Valar quits the app, applies the change, and reopens it. On Windows, Claude Desktop stays in the notification area after its windows close, so Valar ends the app a few seconds after asking it to close.
--force: approve that restart without a prompt, for examplevalar claude-desktop on --direct --force.
--force is supplied.
History and MCP servers on the direct lane
On the proxy lane, Claude Desktop keeps its normal history and MCP servers unchanged. The direct lane runs the app in a separate provider profile. When you switch lanes, Valar copies your local Code sessions (and local Cowork sessions on macOS) and scheduled tasks between the two, and never deletes a session. It also adds your local MCP servers to the direct-lane profile each time you turn the direct lane on. Chat history is stored by Claude and is not affected. To distribute a fixed list of servers for the direct lane, place a JSON array at~/.valar/claude/desktop-mcp.json (%USERPROFILE%\.valar\claude\desktop-mcp.json on Windows), in the schema Claude Desktop uses for managed MCP servers (name, transport, then command/args/env or url/headers). An entry there replaces any server with the same name. The file is read whenever Valar writes the profile; a file that is not valid JSON stops the command with an error rather than being skipped.
Check routing
Quota-first: use your own subscription first
With Desktop on the proxy lane and signed into an eligible Claude account:Turn off routing
Provider profile details
Files and backup
Files and backup
The direct lane writes a Valar profile to Claude Desktop’s provider-profile folder:
It records the Valar endpoint, coding key, model list, and request-attribution headers.The pre-enable profile configuration is backed up at
~/.valar/claude/desktop-backup.json (%USERPROFILE%\.valar\claude\desktop-backup.json on Windows). OFF restores that configuration; it removes the configuration tree if Valar created it.Single-session mode
Single-session mode
Open a separate direct-routed instance:It uses
~/.valar/claude/desktop-session-3p (%USERPROFILE%\.valar\claude\desktop-session-windows\Claude-3p on Windows) and keeps its history there. Your main app’s configuration, login, and reported routing stay unchanged.That folder keeps the instance’s history, not your key. When you quit the instance, valar removes the Valar key from its profile; the next single-session launch writes it again. If the instance ends while valar is not watching (for example, the machine restarts), valar off or valar claude-desktop off removes the key, and so does updating valar. While the instance is open, those commands leave it alone and say so.Only one such instance runs at a time. Add --force to replace an existing instance. Explicit --direct allows this mode even when the shared proxy is provisioned.Security and machine changes
Certificate trust, shared proxy services, and corporate network controls are documented under On-device proxy.Collect CLI logs for support
Inspect~/.valar/cli.log for command/setup failures and valar proxy logs for proxy traffic diagnostics. See Support logs for collection, redaction and rotated history. Review logs before sharing them.
Next steps
On-device proxy
Shared setup, certificates, and network policies.
Claude Code
Configure the terminal CLI separately.