🐛 Hermes 供应商配置用量查询脚本报 401——settings_config 扁平字段未读取凭证

[chenMEME]

Bug Description / Bug 描述

When configuring a Hermes provider (using DeepSeek API via OpenAI-compatible endpoint), the "配置用量查询" (Usage Query) script in the provider edit page returns 401 Unauthorized.

The API key itself is valid — a direct curl to https://api.deepseek.com/v1/user/balance with the same key returns 200 (balance data), and with an empty key returns 401. The bug is in how CC Switch reads credentials from settings_config.

---

Steps to Reproduce / 重现步骤

1. Add a Hermes provider with DeepSeek API (e.g. base_url = https://api.deepseek.com/v1, any API key)
2. Go to the provider edit page
3. Click the "配置用量查询" script test button
4. See 401 Unauthorized error

Root Cause / 根因

In src-tauri/src/commands/provider.rs, the query_provider_usage_inner function, when template_type == TEMPLATE_TYPE_BALANCE, reads credentials from:

let env = settings_config.get("env");
let base_url = env.and_then(|e| e.get("ANTHROPIC_BASE_URL")).and_then(|v| v.as_str());
let api_key = env.and_then(|e| e.get("ANTHROPIC_AUTH_TOKEN")).and_then(|v| v.as_str());

However, for Hermes providers (and potentially other non-Claude providers), settings_config is stored as a flat object:

{
  "api_key": "sk-xxx",
  "base_url": "https://api.deepseek.com/v1",
  "model": "deepseek-v4-flash"
}

There is no env sub-object, so both ANTHROPIC_AUTH_TOKEN and ANTHROPIC_BASE_URL resolve to None → empty credentials → 401 from the upstream API.

Proposed Fix / 修复方案

In provider.rs, the TEMPLATE_TYPE_BALANCE credential reading path should try the flat base_url/api_key fields first, then fall back to the env.ANTHROPIC_* fields for backward compatibility with Claude providers:

// Try flat fields first (Hermes, non-Claude providers), fall back to env.ANTHROPIC_*
let base_url = settings_config
    .get("base_url")
    .and_then(|v| v.as_str())
    .or_else(|| env.and_then(|e| e.get("ANTHROPIC_BASE_URL").and_then(|v| v.as_str())));
let api_key = settings_config
    .get("api_key")
    .and_then(|v| v.as_str())
    .or_else(|| env.and_then(|e| e.get("ANTHROPIC_AUTH_TOKEN").and_then(|v| v.as_str())));

Temporary Workaround / 临时解决方法

If you cannot recompile CC Switch, you can manually edit the SQLite database at ~/.cc-switch/cc-switch.db:

UPDATE providers SET settings_config = json_set(
  settings_config,
  $.env.ANTHROPIC_AUTH_TOKEN,
  $.api_key,
  $.env.ANTHROPIC_BASE_URL,
  $.base_url
)
WHERE id = <provider_id>;

Then restart CC Switch. Note: re-editing the provider in the UI may overwrite settings_config and drop the env field, requiring a repeat of this workaround.

Environment / 环境

• CC Switch Version: (latest, date: 2026-05-20)
• OS: Windows
• Related App: Other / 其他 (Hermes agent via custom provider)

[DOIT-Ben]

本地已修复并验证其中的凭证读取问题：Hermes / OpenClaw 这类扁平 settings_config provider 的用量查询会读取 api_key / base_url，不再只从 env.ANTHROPIC_* 取值，因此不会因为空凭证触发 401。

验证：

• cargo test --manifest-path src-tauri\\Cargo.toml usage_script --lib -- --nocapture

说明：本次修复聚焦“扁平字段未读取凭证”的 401 根因；如果还有特定供应商接口字段差异，可以继续补充返回体样例再单独处理。

[farion1231]

根据本轮 issue 清理，v3.15.0 / v3.16.0 的提交、Changelog、Release Notes 以及本 issue 中的修复验证记录显示该问题已经修复或已被最新版本覆盖，所以先关闭。

如果你在最新版本中仍能复现，请带上版本号、系统环境、复现步骤和相关日志回复这个 issue，我们会重新打开继续跟进。