The proxy runs on macOS, Windows 11 and Linux. It currently supports Claude Code (
claude), Claude Desktop (claude-desktop) and Cursor (cursor). Claude Desktop is not supported on Linux yet, so on Linux the proxy carries Claude Code and Cursor. On Windows, Cursor needs the proxy. Codex, opencode, Pi, Oh My Pi and GitHub Copilot use it too when it is installed; see Forwarder lane.Set up the proxy
You need the Valar CLI and a coding key and a supported harness. On macOS you also need administrator access for certificate trust and proxy settings, and on Windows and Linux for certificate trust. Run these commands from the account that will use Valar:<harness> with a supported harness name:
How harness traffic reaches the proxy
On macOS and Windows,valar proxy enable changes no network setting by default. Each harness’s on command points that harness at its own listener. valar claude on writes the proxy setting into Claude Code’s settings, which carry both the terminal and Claude Desktop’s Code tab. An administrator may still deliver a proxy setting for Claude Desktop through managed settings or a PAC; see Administrator-managed traffic steering.
On a network with a company proxy, Desktop’s Code tab uses that proxy and is not routed. Where the company proxy is fixed, use valar proxy enable --ingress pac.
--ingress pac writes Valar’s automatic-proxy document into the machine’s network settings. The sections below that describe Valar’s automatic-proxy document apply to this option. Running valar proxy enable again keeps the option the machine was set up with; pass --ingress to change it. After valar proxy disable, the next valar proxy enable uses the default.
Routing controls
On an established proxy setup, ordinary ON/OFF toggles do not restart sessions. OFF stops inspection and Valar routing; new connections pass through the local proxy to their original destination without decryption. Proxy settings stay installed so the next ON needs no restart. Changes to the certificate, connection settings, or routing lane may require one.
The services remain available when all harnesses are OFF. To remove them, follow Remove the proxy.
Forwarder lane
With the proxy installed,valar <harness> on also connects Codex, opencode, Pi, Oh My Pi and GitHub Copilot through it, on the forwarder lane. A tool on this lane picks up a new valar login without a restart. on prints the lane it chose; add --direct to keep a tool on its own settings. Cursor on the proxy lane picks up a new valar login without a restart too, whichever credential its settings hold.
If on reports that the forwarder’s port is in use, move it:
valar proxy disable refuses while a tool is on the forwarder lane; run valar <harness> off first.
Subscription-first routing
The proxy can apply subscription-first routing for integrations that support it. Today, quota-first for Claude is shared by Claude Code and Claude Desktop. It uses eligible included allowance before Valar; other harness subscriptions are not supported.--quota-first=false to send all routed inference through Valar. Turning the preference off does not turn a harness off.
See the harness documentation for supported accounts, model selection, counters, and reset commands.
Status and logs
status reports the services, listeners, certificate, and enabled harnesses. logs prints recent proxy activity; -f keeps following it.
To verify Valar forwarding, send a request that uses Valar, then check the harness:
Corporate networks
Valar does not silently replace an existing corporate proxy or automatic-proxy policy. Configure the two directions separately:
Corporate PAC and an upstream proxy work together. Provision without replacing the corporate PAC, and explicitly configure the onward connection:
--cert and --key when using organization-managed certificates. The upstream setting applies to every harness using this proxy, including subscription requests, other forwarded traffic, and undecrypted passthrough. Direct-lane sessions do not use this setting.
Outbound corporate proxy
If your shell already sets an outbound proxy, explicitly approve the same URL:CONNECT:
CONNECT api.anthropic.com:443. Valar selects the destination; the corporate proxy applies its access policy and carries the connection. It must allow both destinations. The hostname changes if you configured another Valar endpoint.
Supply an HTTP or HTTPS proxy endpoint, not the URL of a .pac file. Valar does not evaluate PAC JavaScript or inherit its destination-specific proxy choices. If your PAC selects several corporate proxies, ask IT for one endpoint that can reach all required destinations.
The corporate proxy can be unauthenticated or use Basic authentication: http://user:[email protected]:8080, with reserved characters percent-encoded. NTLM, Kerberos and browser-based sign-in are not supported, which rules out most Windows proxies that use integrated Windows authentication. Ask IT for an endpoint that accepts Basic or no authentication for the destinations below. The proxy credential is separate from your Valar coding key.
If the corporate proxy inspects TLS, its certificate chain must be trusted on the machine. Do not disable TLS verification. Test both a Valar-served request and an original-service request after setup.
The URL is saved in a user-only local file and its credentials are redacted in status output. The command-line argument itself can still appear in shell history or process listings; use your organization’s approved secret-handling process.
A later proxy enable preserves the saved upstream if you omit the flag. Use --upstream-proxy <new-url> to replace it. --upstream-proxy="" clears it only when no conflicting outbound proxy remains in the shell. Never point the upstream at a Valar loopback listener.
How this relates to HTTPS_PROXY
Programs launched from your shell can use itsHTTPS_PROXY value if they support that variable. It does not configure the Valar daemon. The daemon reads only its saved upstream setting, which prevents it from accidentally proxying back to itself.
- If
HTTPS_PROXYalready points to a corporate proxy,proxy enablerequires the same URL to be explicitly approved by--upstream-proxy, or already recorded from an earlier setup. - Claude Code’s own proxy settings point to its local Valar listener after
on. Its requests then travel through Valar and onward through the configured corporate proxy. - A managed proxy setting takes precedence over user settings. IT must point it to the correct local listener; configuring an upstream does not override managed policy.
- The
valarcommands themselves use standard proxy environment settings for their HTTP calls. On a PAC-only network that blocks direct access, provide the corporateHTTPS_PROXYvalue to CLI setup/upgrade commands as well. The saved daemon upstream is not a proxy setting for every program on the machine.
A proxy set in network settings
A fixed proxy in the machine’s network settings (on Windows, Use a proxy server in Settings > Network & internet > Proxy) is treated the same way asHTTPS_PROXY. Apps that read the automatic-proxy document try it before the fixed proxy, so Valar’s document would otherwise move those apps off your corporate proxy. proxy enable therefore stops and names the proxy until you approve that exact proxy:
- Hosts Valar routes try the local Valar proxy first, then your corporate proxy.
- Hosts on the proxy’s bypass list and local addresses connect directly, as before. On macOS, plain host names do too.
- Every other host goes to your corporate proxy.
proxy enable also stops when network services name different proxies or different bypass lists, or when a bypass entry cannot be reproduced exactly. It names the entry so you can rewrite it. valar proxy status warns if the network setting later changes to a proxy that is not approved.
A machine set up with an earlier release over a fixed proxy keeps working as it did. valar proxy status warns that other apps are bypassing that proxy and shows the --upstream-proxy command that fixes it.
Automatic proxy discovery (WPAD)
Automatic proxy discovery does not stopproxy enable. When discovery is on (on Windows, Automatically detect settings, which is on by default), proxy enable checks whether the current network publishes a proxy script. Apps such as Claude Desktop use a discovered script ahead of Valar’s document, so on a network that publishes one, Claude Desktop may not be routed through Valar. proxy enable and valar proxy status warn only in that case. To route Claude Desktop there, IT can add the Valar rule to the published script and provision with --ingress external, as described below.
Administrator-managed traffic steering
If IT owns the automatic-proxy policy or managed app settings, provision without replacing them:
On Linux there is no automatic-proxy document and no machine-wide proxy setting.
--ingress and --pac-port do not apply there; each harness’s on command points that harness at its own listener.
Use valar proxy status for the installed addresses. Set custom ports with --port <harness>=<port>, --port forward=<port> and --pac-port <port>. Existing corporate outbound proxy requirements still apply with external steering; combine --ingress external with --upstream-proxy when both are needed.
Add Valar to an existing corporate PAC
Keep the corporate PAC URL. Add an exact-host rule for supported traffic before the existing catch-all rules. For the current PAC-based integration, Claude Desktop, use its listener (18080 by default):
FindProxyForURL to CorporateProxyForURL without changing its body, then add the wrapper. The selected host uses the new local-proxy rule; all other hosts retain their existing corporate rules. Review that override with IT. The final function above is only a minimal example. Deploy this PAC change only to devices where Valar is provisioned. Keep local proxy/PAC addresses reachable without sending them back through another proxy.
The semicolon-separated return value is a fallback list, not a chain. The app tries the local proxy first and may try the corporate proxy directly if the local proxy is unavailable. To make a healthy local Valar proxy send onward through the corporate proxy, you still need --upstream-proxy.
Choose the failure policy with IT:
Do not append
DIRECT if your organization prohibits direct internet access. PAC fallback is client-dependent and does not guarantee retrying an active request or bypassing HTTP errors. An upstream refusal returned by Valar is not the same as an unreachable local proxy.
A PAC function receives a URL and host, not the calling application’s identity. This host rule also affects other PAC-aware apps requesting that host. They reach the Desktop listener and follow its routing switch, with one exception: the Claude in Chrome extension is always passed through to Anthropic on its own login. Review that scope with IT; do not send multiple harnesses to one listener when you need independent controls.
Configure harnesses that do not use system PAC
Cursor does not use the system PAC either;valar cursor on points Cursor’s own http.proxy setting at its listener.
Claude Code does not use the system PAC for its proxy connection. Run valar claude on to configure its listener, or merge equivalent proxy values into IT-managed Claude settings:
/Library/Application Support/ClaudeCode/managed-settings.json on macOS and C:\Program Files\ClaudeCode\managed-settings.json on Windows. Merge the proxy settings into the existing policy without replacing the whole file. For NO_PROXY and no_proxy, add the listed loopback addresses to your required internal bypasses rather than replacing the existing lists. Neither list should exclude api.anthropic.com or use *, which would bypass Valar. A conflicting lowercase proxy value can take precedence over uppercase, so keep both forms consistent. Use the installed listener address if you changed the default port.
Even when IT delivers the connection settings, run the harness’s on command to enable Valar routing. Settings alone do not turn its routing switch on.
Roll out and verify corporate networking
- Provision with
--ingress external, the corporate upstream, and trusted certificates. - Deploy the PAC rule and any app-specific proxy settings to the selected devices.
- Activate each supported harness and follow any restart prompt. A PAC update can remain cached in a running app.
- Check
valar proxy statusforexternalingress and the redacted upstream. Check each harness’s status and send a Valar-served request. - Run each harness’s
status --verify. Test subscription/native traffic separately; successful Valar verification confirms only the Valar path. - In a pilot device, test your chosen local-proxy failure policy and confirm the corporate proxy sees the intended destinations.
Certificates and machine changes
By default, setup:- Creates a local root certificate named Valar Local Root CA and trusts its public certificate: in the System keychain on macOS, in the computer’s certificate store (
LocalMachine\Root) on Windows, and on Linux in the system certificate store and two places of your own (see On Linux). - Uses its private key once to sign a leaf certificate covering the supported harness destinations, then discards the root private key without saving it to disk.
- Stores the leaf certificate and private key under
~/.valar/proxy/with user-only permissions. - Installs two per-user background services: the proxy and the automatic-proxy document server. On Linux it installs one: the proxy, as a systemd user service.
- Configures the automatic-proxy URL, unless you selected external steering: on each enabled network service on macOS, and in your Windows proxy setting (Use setup script) on Windows. On Linux it writes no machine-wide proxy setting; each harness’s
oncommand sets that harness’s own proxy setting.
V1A-1015), because the listening ports are shared by every account.
On Windows
Setup asks Windows for administrator access once, to add the Valar root certificate to the computer’s certificate store; choose Yes. Everything else it changes belongs to your own account. If you choose No, or cannot enter an administrator’s credentials, setup stops without changes (V1A-1001). Ask an administrator, or have your IT team set it up from their deployment tool. If Windows does not trust the certificate once it is added, setup takes it out again and stops (V1A-1124); deploy an organization-managed certificate instead.
A machine set up with an earlier version keeps its certificate in your own certificate store until the certificate is renewed. The renewal puts the new certificate in the computer’s store: Windows asks for administrator access, then asks you to confirm removing the old one.
Setup stops before making changes when:
- A policy makes Windows use one proxy setting for every user of the machine (
V1A-1125). Your own setting would be ignored, so have IT add the Valar rule to the machine’s script and provision with--ingress external. See Administrator-managed traffic steering. - A port it needs is in use or inside a range Windows reserves for Hyper-V or WSL (
V1A-1121). Runnetsh interface ipv4 show excludedportrange protocol=tcpto list the reserved ranges, then pick another port with--portor--pac-port. - It would create a certificate but no one is at a terminal to approve Windows’ administrator prompt (
V1A-1128). For unattended installs, run it from your deployment tool as SYSTEM, or use an organization certificate. See Roll out with MDM.
On Linux
Setup asks for administrator access once, throughsudo, to add the Valar root to the system certificate store. Everything else it changes belongs to your own account.
- Certificate trust is in three places. Cursor’s chat reads the system certificate store. Cursor’s window reads only your NSS certificate database (
~/.pki/nssdb). Claude Code trusts the Valar root through its own settings in~/.claude/settings.json. Setup adds the root to all three. - Supported distributions. Setup updates the system certificate store on Debian, Ubuntu, Fedora, RHEL, Arch, openSUSE and distributions built on them, such as Linux Mint, Rocky and Manjaro. Where it can’t, it asks for no password: Claude Code still uses the proxy, and Cursor uses the direct lane (in Valar only mode,
valar cursor onstops instead). - Without a terminal to ask on, setup stops without changes (
V1A-1001). A passwordlesssudorule forvalaralso works. - Cursor needs
certutil. It adds the root to your NSS database, and most distributions do not install it by default. Installlibnss3-toolson Debian and Ubuntu,nss-toolson Fedora and RHEL, ornsson Arch, then runvalar proxy enableagain. Without it, setup still succeeds and Claude Code is routed;valar cursor onnames the package to install. - The proxy runs while you are logged in. It is a systemd user service, so it starts at login and stops at logout. A session left running after logout, such as one in
tmux, loses its proxy. To keep the proxy running after logout, an administrator can runsudo loginctl enable-linger <user>.valar proxy statuswarns when this is off. - A systemd user session is required. A container, WSL 1, or an account nobody is logged in to has none. Setup stops there without changes (
V1A-1130). Log in, or have an administrator run theloginctlcommand above. - WSL 2 is not yet supported. Inside WSL,
cursoris the Windows app, so set up Cursor from Windows. - One user owns the proxy on a machine. The listening ports are shared, so setup refuses while another account’s proxy is running (
V1A-1015), and the proxy drops connections from other accounts.
valar proxy enable to apply Valar-managed automatic-proxy settings to it. On Windows, the setting covers Wi-Fi and Ethernet, so a new network of either kind needs no action. A VPN built into Windows keeps its own proxy setting, which Valar does not change. With --ingress external, have IT update its managed proxy settings or PAC coverage instead. Verify routing on the new connection.
Installed files and cleanup
Installed files and cleanup
These paths are relative to
~/.valar/ (%USERPROFILE%\.valar\ on Windows) unless noted. The removal column describes a successful valar proxy disable; partial cleanup keeps the installation record for retry.Organization-managed certificate trust is preserved. Valar removes only the root certificate whose fingerprint this installation recorded as Valar-generated. Files you placed alongside the proxy’s own files are not removed.
Organization-managed certificates
If your organization supplies the certificate, trust its root through your normal device-management process, then run:api.anthropic.com and, for Cursor, *.cursor.sh, *.api5.cursor.sh, *.us.api5.cursor.sh and *.global.api5.cursor.sh. If it does not cover Cursor’s names, valar cursor on lists the names to add. It then stops without changing Cursor, except side by side on macOS, where it sets up Cursor without the proxy.
On macOS, root-run provisioning can read protected certificate/key sources without changing their ownership or permissions. Symlinked paths are supported; their targets must be regular PEM files. Without root, both sources must be readable by the user; otherwise rerun the same provisioning command with sudo. The installed copies remain private to the selected user.
On Linux, deliver your root to two places: the system certificate bundle, for Claude Code and Cursor’s chat, and each user’s NSS database (~/.pki/nssdb), for Cursor’s window. With --cert and --key, setup adds no trust of its own and asks for no administrator access. This is the unattended path for a Linux fleet. One exception: on a machine that already used a Valar-generated certificate, switching asks for administrator access once, to remove that certificate from the system store. Without it, setup finishes but warns that the old certificate is still trusted; run valar proxy enable again from a terminal, or grant the passwordless sudo rule, to remove it.
Valar copies the leaf and key into its protected local directory. It does not create, rotate, or remove your organization’s root CA. Renew organization-managed certificates through your PKI and rerun setup with the replacement files.
valar proxy restart keeps a healthy certificate. If a Valar-generated certificate needs replacement, it can request administrator access on macOS and Linux, or show the Windows certificate warning, to install a fresh one. A replacement certificate may require restarting affected apps.
Create an organization-managed certificate
Use your existing PKI when available. The example below creates a private root and one device leaf on a protected signing machine. Keep the root key there; distribute only the root’s public certificate through MDM and the device’s leaf bundle/key through a protected channel. Issue a separate leaf key for each device.1. Create the root once, on the signing machine
1. Create the root once, on the signing machine
Use a new directory for a new CA. Do not overwrite an existing CA when enrolling another device.
root.key can issue certificates trusted by enrolled devices. Store it offline or in your PKI’s protected signing system. Never deploy it to user devices. The validity periods in this example are choices for your PKI to review, not Valar requirements.2. Issue a leaf for each device
2. Issue a leaf for each device
Run from the CA directory. Choose a new directory name for each device or renewal; this example uses The supported destinations are
device-001.api.anthropic.com and, for Cursor, *.cursor.sh, *.api5.cursor.sh, *.us.api5.cursor.sh and *.global.api5.cursor.sh. Update SANs when the supported harness destinations change. This example root signs device leaves directly; its pathlen:0 constraint does not permit intermediate CAs. If you use an existing PKI with intermediates instead, include them after the leaf in the bundle. Root inclusion is optional; trust must still be installed separately.The recipe uses real extension files and an explicit serial-file path, so it works with macOS LibreSSL and OpenSSL. Serialize issuance when using this simple shared serial file; production PKI should manage issuance and serial numbers.3. Verify before distributing
3. Verify before distributing
OK, and cmp should exit successfully. Confirm the leaf has CA:FALSE, server authentication usage, and the required SAN. These checks validate the issued files; they do not install macOS trust. valar proxy enable also checks hostname coverage, validity, matching keys, and the machine’s trust store before accepting the certificate.Trust and distribute
The leaf private key must be an unencrypted PEM file so the background service can start unattended. Protect it through filesystem permissions and secure delivery. PKCS#8, SEC1 EC, and PKCS#1 RSA encodings are supported. This file-based setup does not accept a keychain-only or hardware-key reference.
Wait for the MDM trust profile to apply before provisioning. For a controlled manual pilot, your administrator can install the public root into the macOS System keychain:
Renew certificates
Issue a new device leaf before expiry, verify it, then rerunproxy enable --cert ... --key ... with the new files. Replacing source files or updating their symlinks alone does not replace Valar’s installed copies. Reapply each routed harness’s on command and follow any restart instructions; verify forwarding afterward.
When rotating the root, distribute and verify the new trust profile before provisioning leaves signed by it. Keep the old root until devices have moved, then retire it through your MDM/PKI process. Valar does not manage organization certificate revocation or trust-profile removal.
Endpoint security tools
An endpoint security tool (EDR or antivirus) can stop the proxy, block its local listeners, or block its certificate. When that happens, harness requests fail before they reach Valar. Ask your security team to allow Valar before you roll it out.Allow Valar’s file paths, not the file hash
valar updates regularly, and each release is a new file. A rule that matches the file’s hash (SHA256) covers one release only, so the next update is blocked. Allow Valar’s file paths instead. Their names stay the same from release to release. Allow these exact files, not their folders: a folder rule would also allow anything else placed there.
macOS
After an upgrade,
~/.local/bin/valar is a link to the release’s own copy, in a folder named by its checksum. Security tools usually see that copy as the running file, so allow both paths.
Windows
Windows cannot replace a running program, so the proxy runs its own copy of
valar.exe.
If you installed with VALAR_PREFIX or from MDM at another path, such as /usr/local/bin/valar, use that folder in place of ~/.local/bin. The .valar-versions-valar folder and the check copies sit next to the CLI.
Before you roll it out, test on one machine under your policy: run valar proxy enable, turn on a harness, and send a request. When a new release is available, also run valar upgrade to confirm the rules cover an update.
What the allowed process does
- Runs as a per-user background service: launchd agents
ai.valarhq.valar.proxyandai.valarhq.valar.pacon macOS, or Task Scheduler tasks\Valar\ai.valarhq.valar.proxyand\Valar\ai.valarhq.valar.pacon Windows. - Listens on this machine only, on
127.0.0.1and::1, ports18080to18083by default, or the ports you configured. - Inspects TLS for the supported harness destinations, using the certificate described in Certificates and machine changes. A tool that blocks local TLS inspection must allow it for these destinations.
- Changes proxy settings for the harnesses it routes: macOS automatic proxy settings, the Windows proxy setup script, and Cursor’s
http.proxysetting. - Connects to
api.valarhq.aion port 443, or your configured Valar endpoint, and to the services the harness itself uses, such as Cursor’s servers.
valar proxy status. Then send one request from each harness you route. For Claude Code and Claude Desktop, valar claude status --verify and valar claude-desktop status --verify fail unless the proxy has forwarded a request for that harness. For Cursor, run valar cursor status and check that a message on a Valar model is answered.
Deploy with MDM
See Roll out with MDM for deploying the CLI, the proxy, and each harness from Jamf, Kandji, Intune, or other MDM tools.Remove the proxy
- Run
valar proxy statusto see which harnesses use the proxy. - Run
valar <harness> offfor each harness still on the proxy lane. - Save active work. If IT manages proxy settings or PAC rules, have IT remove the local Valar pointers and reload affected apps.
- Remove the shared component:
proxy disable refuses while any harness remains on the proxy lane, even with --force. Once all are OFF, it checks for running sessions that may still depend on the proxy and asks before proceeding. Read the restart instructions: automatic restart is available only where supported; other sessions need a manual restart.
For unattended removal, --force approves this interruption. --no-restart suppresses automatic app restarts and leaves that work to your deployment process. Neither flag makes a running session independent of the proxy.
Turn everything off in one command. valar off --proxy turns every harness off and then removes the proxy exactly as valar proxy disable does, with the same checks, so an unattended run still needs --force. It exits non-zero while anything on the device still sends traffic to Valar, and lists what remains: a harness that is still routed, the proxy or its root certificate, or an automatic proxy setting that names Valar. Plain valar off keeps the proxy installed.
Removal clears Valar-owned automatic-proxy settings, removes its services and proxy files, and removes only a root certificate recorded as generated by this installation. It preserves organization-managed trust and the CLI support log. With external steering, IT must remove its own proxy pointers.
Check the exit code and run valar proxy status. If removal is incomplete, fix the reported cause and retry. Do not delete the installation records by hand while recovery is pending.
Verify certificate removal
Verify certificate removal
For a Valar-generated root, record Compare the reported SHA-256 hashes with the recorded fingerprint, ignoring colons and letter case. The recorded fingerprint should no longer appear. Another certificate with the same name may remain if it belongs to your organization or another installation; do not delete certificates by name alone.On Windows, list the matching certificates in your user store instead:Compare each SHA-256 hash with the recorded fingerprint the same way.On Linux, list your NSS database:Valar’s entry is named
root_fingerprint from ~/.valar/proxy-state.json before disabling the proxy. Successful cleanup removes that file. This check does not apply to organization-managed roots, which Valar leaves in place.After valar proxy disable, list matching certificates in the System keychain:Valar Local Root CA followed by the first 16 hex digits of the recorded fingerprint. After removal, that entry should be gone. Another entry with the same display name is not Valar’s to remove.These commands only read the certificate store. If the recorded certificate remains, follow the removal error and retry valar proxy disable. A warning about a remaining trust setting after its certificate was removed is a separate cleanup issue; it does not mean the certificate is still installed.Deployment checks and diagnostics
Use exit codes to detect failure, then read the full error and its next steps. A nonzero exit can describe partial completion; do not assume every file or service was rolled back.
The local services run as the selected user under
~/Library/LaunchAgents/. Their labels are ai.valarhq.valar.proxy and ai.valarhq.valar.pac. From that user’s session, inspect them without changing state:
valar proxy diag runs on macOS only. On Linux, use valar proxy status, valar proxy logs and the commands above.
After successful removal, both service lookups should report that the jobs are absent. With external ingress, the corporate PAC can remain configured; IT must remove the local Valar rules. With Valar-managed PAC, macOS may keep a disabled URL string. An enabled stale pointer still needs cleanup.
Troubleshooting
A session that still depends on an unavailable proxy can fail until the service is restored or its connection settings are reloaded. Some integrations can fall back to a direct connection; that does not prove Valar routing. Verify each harness after setup or repair.
For command/setup failures, collect the CLI support log. For service startup failures, inspect
~/.valar/proxy.boot.log and ~/.valar/pac.boot.log (under %USERPROFILE%\.valar\ on Windows).
Support logs
The CLI writes command and setup diagnostics automatically to~/.valar/cli.log; no logging option is needed. Logging is best effort: a permissions problem or an early refusal can prevent a record, so keep the terminal error too.
Collect logs and check their contents
Collect logs and check their contents
The CLI support log records command names, CLI/OS versions, exit codes and sanitized errors. Proxy setup failures can also include network-service names and proxy-setting classifications.It does not record full command arguments, configuration or environment contents, request bodies, or proxy traffic. Error text is sanitized to redact recognized credentials, argument values, URLs, account names and absolute paths. Review the file before sharing it.Rotation keeps the live log and one
~/.valar/cli-<timestamp>.log backup, about 2 MiB combined. The live file has the latest records; include the backup if support needs older history. Both survive valar proxy disable.valar proxy logs and the service-startup logs are separate diagnostics; the CLI support log’s redaction rules do not apply to them. Review those logs separately before sharing.