Skip to content
CC Switch WikiUnofficial Community Wiki

toggling Send User-Agent silently removes every unrelated custom header - cc-switch

Quick fix

Do not toggle Send User-Agent in the OpenClaw provider editor; upgrade and wait for a fix, as the switch replaces or deletes the entire headers object.

Symptom

Section titled “Symptom”
Error output
enabling leaves only the default User-Agent header; disabling or an on/off round trip removes `headers` entirely

Cause

Section titled “Cause”

In the cc-switch OpenClaw provider editor, the Send User-Agent switch does not only add or remove that request header. It destructively updates the entire headers object: enabling it replaces headers with an object containing only the default User-Agent, while disabling it deletes the entire headers object. The loss also occurs if you turn the switch on and then off before saving; the damaged configuration is carried into the final form submission. The problematic code is in the destructive header update logic in useOpenclawFormState.ts (L160-L169), which writes the form configuration through ProviderForm.tsx and into the submission payload. The issue author reproduced this offline with jsdom against the 3.20.4 source (commit bfaaba16): 6 of 14 diagnostic tests failed preservation checks (enable, disable, and round-trip each failed at both the hook and final submission layers); 8 control tests passed, including saving without touching the switch, enabling when headers were absent, removing only User-Agent, and confirming non-header fields were unaffected. The hook was byte-for-byte identical on the then-current main branch (commit 372b1698), so the same issue also existed there. The issue is closed, but the report does not specify a fixed version. The author's suggested fix is to merge the default User-Agent into existing headers when enabling, and when disabling, remove only User-Agent and delete the entire object only if headers becomes empty.

Fix

Section titled “Fix”

  1. Until a fixed version is released, do not touch the Send User-Agent switch when editing an OpenClaw provider. If you leave it alone, opening and saving directly preserves existing custom request headers; the issue's control tests confirmed this path is lossless.

  2. If you already toggled the switch and lost headers, manually restore the deleted custom request headers in the provider configuration (such as X-Fixture and X-Other). After saving, avoid toggling the switch again.

  3. Upgrade to a cc-switch version that includes the fix. The correct behavior suggested by the issue author is to merge the default User-Agent into existing headers when enabling, and remove only User-Agent when disabling, deleting the entire object only if headers is empty. After upgrading, verify with a non-critical provider configuration that custom request headers remain after toggling the switch on and off.

Affected Versions

Section titled “Affected Versions”
Toolcc-switch（OpenClaw 供应商编辑器）
Version3.20.4（受影响；在当时 main 分支 commit 372b1698 上同样存在；修复版本未注明）
PlatformsUnknown

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”
Will custom request headers be lost if I only open the editor and save without touching this switch?
No. The issue's control tests confirmed that hydration and saving without touching the switch preserve the original headers; loss occurs only when enabling, disabling, or turning it on and then off.
Does this bug affect configuration fields outside headers?
No. The 8 passing control tests included a check that non-header configuration fields were preserved. Only the headers object is affected.
Is there a problem enabling this switch if the configuration originally had no custom request headers?
No. The control tests covered enabling when headers were absent, and that path passed. Existing custom request headers are the ones that get overwritten and lost.
Section titled “Related problems”
1-hour cache write cost undercounted by 37.5%: ClaudeUpdate Claude Code to a version containing this fix so 1-hour cache writes are billed at 1.6 times the 5-minute cache write rate.1 issues mergedtotal_cost_usd = 0: Claude CodeAdd pricing for claude-opus-5-5 to the model_pricing seed data to prevent imported request costs from being recorded as $0.1 issues mergedCodex session import ignores cache_write_input_tokensUpgrade cc-switch or wait for an official fix: Codex session log import misses cache_write_input_tokens, so cache writes are counted as ordinary input and…1 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.