Commit Graph

1587 Commits

  • feat: Add Codex OAuth FAST mode toggle (#2210)
    * Add Codex OAuth FAST mode toggle
    
    * fix(codex-oauth): default FAST mode to off to avoid surprise quota burn
    
    service_tier="priority" consumes ChatGPT subscription quota at a higher
    rate. Users must now opt in explicitly rather than inherit FAST mode
    silently when this feature ships.
    
    ---------
    
    Co-authored-by: Jason <farion1231@gmail.com>
  • [codex] Stabilize Codex OAuth cache routing (#2218)
    * Stabilize Codex OAuth cache routing
    
    Codex OAuth-backed Claude proxy requests now reuse a client-provided session identity for prompt cache routing and send Codex-like session headers when that identity exists. Generated proxy UUIDs are intentionally excluded so they do not fragment cache locality.\n\nThe same path exposed two runtime issues during validation: rustls needed an explicit process crypto provider, and Codex OAuth can return Responses SSE even when the original Claude request is non-streaming. Those are handled so cache-routed requests can complete instead of panicking or being parsed as JSON.\n\nConstraint: Official Codex uses conversation identity and Responses session headers for prompt cache routing.\nRejected: Always use generated proxy session IDs | generated IDs change per request and reduce cache reuse.\nConfidence: medium\nScope-risk: moderate\nDirective: Do not remove the client-provided-session guard unless generated session IDs become stable per conversation.\nTested: cargo test codex_oauth\nTested: Local dev app health check on 127.0.0.1:15721\nTested: Local proxy logs showed cache_read_tokens after restart\nNot-tested: Full cargo test without local cc-switch port conflict\nRelated: #2217
    
    * feat(proxy): aggregate forced Codex OAuth SSE into JSON for non-streaming clients
    
    Narrow override on top of #2235's streaming fallback.
    
    Codex OAuth always forces upstream openai_responses into SSE, even
    when the original Claude request is stream:false. #2235 handles this
    by routing such responses through the streaming transform so the
    client receives text/event-stream — that avoids the 422 that JSON
    parsing would produce, and it also protects any other provider that
    unexpectedly returns SSE (the response.is_sse() guard).
    
    But for Claude SDK callers that sent stream:false, returning SSE
    still violates the Anthropic non-streaming contract. This commit
    adds an override on exactly one combination — non-streaming client
    + codex_oauth + openai_responses — to aggregate the upstream
    Responses SSE into a synthetic Responses JSON and then run the
    regular responses_to_anthropic non-streaming transform. All other
    paths, including the generic response.is_sse() fallback, remain
    on the streaming path from #2235.
    
    The aggregator reuses proxy::sse::take_sse_block / strip_sse_field,
    which support both \n\n and \r\n\r\n delimiters; a hand-rolled
    split("\n\n") would silently fail on real HTTPS upstreams.
    
    Tests cover the happy path, CRLF delimiters, response.failed
    errors, and the missing response.completed defensive branch.
    
    ---------
    
    Co-authored-by: Jason <farion1231@gmail.com>
  • fix: use TOML parser instead of regex for Codex model extraction (#2222) (#2227)
    * fix(codex): use TOML parser instead of regex for model extraction
    
    Regex only matched model=... on first line, TOML parser handles
    multiline TOML correctly.
    
    Fixes #2222
    
    * fix(stream_check): drop unused regex::Regex import
    
    The previous commit replaced the only Regex usage in stream_check.rs
    with toml::Table parsing, leaving `use regex::Regex;` orphaned.
    Without this removal, `cargo clippy -- -D warnings` (run in CI)
    fails with `unused import: regex::Regex`.
    
    ---------
    
    Co-authored-by: Jason <farion1231@gmail.com>
  • fix(skills): prevent duplicate imports when import button is double-clicked (#2211)
    Closes #2139
    
    Two related defects let the installed-skills count balloon when users
    tap the import confirm button multiple times — either deliberately or
    because the button is still clickable while a slow import is in flight:
    
    - The confirm button only disabled itself while `selected.size === 0`,
      so it stayed clickable during a pending mutation. Each extra click
      triggered another `importFromApps` mutation.
    - `useImportSkillsFromApps` appended the server response to the
      installed cache without deduping, so re-firing the mutation stacked
      the same skills into the list again.
    
    Disable the confirm (and cancel) buttons while the mutation is pending
    — matching the `isRestoring` / `isDeleting` pattern already used by
    `RestoreSkillsDialog` — and merge success payloads by
    `InstalledSkill.id` so repeated results overwrite rather than
    accumulate.
    
    The merge is extracted as a pure `mergeImportedSkills` reducer to make
    the behaviour unit-testable and to short-circuit on an empty payload,
    returning the existing reference so React Query does not notify
    subscribers about a no-op cache update.
  • Style/session manager list UI (#2201)
    * style(FailoverQueueManager): 显示供应商备注信息
    
    * style(FailoverQueueItem): 添加供应商备注字段以支持备注信息显示
    
    * style(FailoverQueueManager): 显示供应商备注信息
    
    * style(FailoverQueueItem): 添加供应商备注字段以支持备注信息显示
    
    * style(FailoverQueueManager): 更新供应商备注信息的显示样式
    
    * style(FailoverQueueItem): 添加条件序列化以优化供应商备注字段
    
    * style(App, SettingsPage, ScrollArea): 调整组件样式以改善布局和视觉效果
    
    * style(App, SettingsPage, ScrollArea): 调整组件样式以改善布局和视觉效果
    
    * style(SettingsPage, useSettings): 统一代码格式,调整样式和变量声明
    
    * style(App): 调整底部内边距以改善布局
  • fix(pricing): correct Kimi K2.6 seed prices to match official rates
    Moonshot's official USD pricing for kimi-k2.6 is $0.95 input /
    $4.00 output / $0.16 cache-hit per 1M tokens (~58-60% higher than
    K2.5). The previous commit copied K2.5's $0.60/$2.50/$0.10, which
    would have under-billed K2.6 traffic in the usage dashboard.
    
    No migration needed since this version is unreleased; INSERT OR
    IGNORE will write the correct values on first launch.
  • feat(presets): upgrade Kimi K2.5 to K2.6 in direct Moonshot configs
    Bump model id and display name from K2.5 to K2.6 in Hermes, OpenClaw,
    OpenCode, and Claude (direct api.moonshot.cn) presets. Pricing,
    context window, and base URL are unchanged.
    
    Add kimi-k2.6 row to model_pricing seed; no migration needed since
    seed_model_pricing uses INSERT OR IGNORE and runs on every startup
    via ensure_model_pricing_seeded. Old kimi-k2.5 row is kept to
    preserve historical usage stats.
    
    Nvidia aggregator forwards (moonshotai/kimi-k2.5) intentionally keep
    the K2.5 SKU until Nvidia's catalog confirms K2.6.
  • docs(release-notes): add v3.14.0 release notes (en/zh/ja)
    Cover Hermes Agent onboarding (6th managed app), Claude Opus 4.7
    rollout, Gemini Native API proxy, "Local Routing" rename,
    application-level window controls, Copilot premium consumption
    deep optimization, session list virtualization, Usage date range
    picker, Stream Check error classification, pricing v8->v9 reseed,
    and related breaking changes.
    
    18 external PR contributions credited in all three locales.
  • docs(changelog): extend v3.14.0 entries with late additions
    Fold six late commits into the v3.14.0 section (Added / Changed / Fixed)
    and refresh the stats header against the actual v3.13.0..HEAD diff:
    100 commits | 219 files | +20,548 / -3,569.
    
    Late additions covered: Hermes dashboard toolbar launch, LemonData
    preset across all six apps, DDSHub Codex endpoint, Hermes toolbar
    icon + MCP reorder, Hermes health-check schema fix, Usage modal
    support for Hermes/OpenClaw.
  • feat(presets): add DDSHub Codex preset
    DDSHub now exposes a Codex-compatible endpoint at the same host as
    its Claude service. Base URL omits the /v1 suffix since the gateway
    auto-routes OpenAI SDK paths.
  • feat(presets): add LemonData provider across all six apps
    Register LemonData (third-party partner) preset for Claude, Codex,
    Gemini, OpenCode, OpenClaw, and Hermes, plus icon assets and i18n
    partner promotion copy (zh/en/ja). Claude preset uses
    ANTHROPIC_API_KEY auth; OpenAI-compatible apps target gpt-5.4.
  • style(hermes): use dashboard icon and move MCP to toolbar end
    Swap ExternalLink for LayoutDashboard on the Hermes Web UI button —
    clicking it may launch `hermes dashboard` rather than just open a URL,
    so a panel-style glyph reads truer than a generic external-link icon.
    Also reorder the toolbar so MCP sits in the final slot, matching the
    claude/codex/gemini/opencode layout.
  • fix(hermes): stop health check from borrowing OpenClaw schema
    Hermes providers were routed through check_additive_app_stream, the
    OpenClaw dispatcher, which reads camelCase fields (baseUrl/apiKey/api)
    and emits "OpenClaw is missing ..." errors. Hermes stores snake_case
    fields (base_url/api_key/api_mode) with different protocol tags, so
    users saw "OpenClaw provider is missing baseUrl" even after filling in
    every Hermes field correctly.
    
    Introduce check_hermes_stream with Hermes-specific extractors. Route
    api_mode (chat_completions / anthropic_messages / codex_responses) to
    the matching check_claude_stream api_format, and return bedrock_converse
    as unsupported. Resolve api_mode before extracting URL/API key so users
    who picked bedrock_converse see the real cause first rather than a
    misleading "missing base_url" message.
  • fix(usage): support Hermes and OpenClaw in usage query modal
    Extend getProviderCredentials to read flat settingsConfig fields for
    Hermes (snake_case base_url / api_key) and OpenClaw (camelCase baseUrl
    / apiKey), so the "official balance" template auto-selects for matching
    providers like SiliconFlow.
    
    Also refactor the BALANCE and TOKEN_PLAN test paths in handleTest to
    reuse the precomputed providerCredentials instead of re-reading
    env.ANTHROPIC_* directly, which previously caused empty key errors for
    non-Claude apps even when the key was configured.
  • feat(hermes): launch dashboard from toolbar when Web UI is offline
    When the Hermes Web UI probe fails, the toolbar entry now opens an info
    confirm dialog offering to run `hermes dashboard` in the user's preferred
    terminal. Accepting spawns it via a temp bash/batch script; `hermes
    dashboard` itself opens the browser once ready, so we do not poll.
    The Memory panel and Health banner keep the existing toast behavior.
    
    Also corrects the stale `hermes web` hint in the offline toast (the real
    command is `hermes dashboard`) and reorders Linux terminal detection to
    try `which` before stat'ing /usr/bin, /bin, /usr/local/bin.
  • docs(changelog): add v3.14.0 release notes
    Summarize the 94 commits since v3.13.0 (216 files, +19,923 / -3,554)
    into Keep-a-Changelog entries: Hermes Agent as the 6th managed app,
    Claude Opus 4.7 rollout, Gemini Native API proxy, Copilot GHES,
    session list virtualization, usage date range picker, and the
    "Local Proxy Takeover" -> "Local Routing" rename.
    
    Breaking changes collected in a dedicated section: explicit Hermes
    api_mode, ANTHROPIC_REASONING_MODEL removal, per-provider proxy
    removal, schema bumps (v8->v9 pricing reseed, v9->v10 Hermes columns),
    and XCodeAPI preset removal.
  • style(providers): apply prettier to common-config hooks
    Reformat three hooks brought in from upstream #2191 so that
    format:check passes in CI.
  • fix(header): stop auto-compact from latching after maximize
    useAutoCompact cached normalWidthRef = el.scrollWidth on every
    non-compact resize, but per DOM spec scrollWidth === clientWidth
    when content fits. Maximizing the window (content no longer
    overflows) therefore wrote the container width into
    normalWidthRef, making it impossible to re-enter compact when
    the window was restored to its original size.
    
    Move the assignment inside the overflow branch so the cache is
    only written at the actual compact threshold, where scrollWidth
    reflects the real content width.
  • style(header): unify toolbar icon button width across apps
    Normalize all icon-only ghost buttons in the header toolbar to
    32x32 (w-8 px-2). Previously Hermes/OpenClaw used default sm
    padding (~40px) while Claude's Skills/Sessions used w-8 px-2,
    so switching apps caused a width jump and put useAutoCompact's
    cached normalWidthRef out of sync across apps.
  • feat(skills): enable Hermes in unified Skills management
    Wire hermes through SkillApps struct, DAO SQL, command parser, and
    SKILLS_APP_IDS. Add a Skills entry to the Hermes toolbar. Simplify
    skill_sync test fixtures to use SkillApps::default().
  • feat(hermes): align provider schema with Hermes Agent 0.10.0
    Hermes 0.10.0 tightened custom_providers validation (commit 2cdae233):
    invalid base_urls are rejected, unknown fields produce warnings, and
    new fields (rate_limit_delay, bedrock_converse, key_env) landed.
    
    - Add bedrock_converse to the api_mode selector (and i18n labels)
    - Expose rate_limit_delay in a provider-level advanced panel
    - Validate base_url client-side (URL shape, template-token friendly)
    - Drop per-model max_tokens — not in _VALID_CUSTOM_PROVIDER_FIELDS
    - Round-trip test asserts set_provider preserves rate_limit_delay /
      key_env / any unknown forward-compat field
  • style: apply prettier and rustfmt
    No behavior changes. Brings three files back in line with the project
    formatters (CI runs `pnpm format:check` and `cargo fmt --check`).
  • test: sync stale fixtures and isolate openclaw env tests
    Three unrelated test failures surfaced after rebase:
    
    - McpFormModal expected the apps boolean set without `hermes`; Hermes MCP
      support is now wired, so the fixture must include `hermes: false`.
    - therouter Gemini preset was bumped to `gemini-3.1-pro` in a later
      commit; update the assertions to match current config.
    - openclaw_config tests mutate process-level `CC_SWITCH_TEST_HOME` and
      `HOME` inside a module-local Mutex, but hermes_config does the same
      under its own separate Mutex. Running both modules in parallel let the
      env races corrupt hermes_config's `with_test_home`. Tag the four
      env-mutating openclaw tests with `#[serial]` so they serialize across
      modules via serial_test's process-wide default key.
  • fix(providers): drop legacy ANTHROPIC_REASONING_MODEL from Claude quick-set
    The model-mapping quick-set button referenced an undefined `reasoningModel`
    prop and wrote `ANTHROPIC_REASONING_MODEL`, which the backend explicitly
    marks as deprecated legacy (see services/provider/mod.rs and
    services/proxy.rs). Remove all three references so typecheck passes and
    the button matches the provider model schema.
  • refactor(hermes): drop "Auto" api_mode and require explicit protocol
    Hermes' built-in api_mode detection only matches a handful of official
    endpoints (api.openai.com, api.anthropic.com, api.x.ai, AWS Bedrock);
    third-party / proxy endpoints silently fall back to chat_completions,
    which causes opaque 401/404s on Anthropic-protocol or Codex-Responses
    providers. The "Auto" option was misleading for the common third-party
    case.
    
    - Drop the "Auto" option from the API Mode dropdown; remove the
      HermesApiModeChoice sentinel type so writes always emit api_mode.
    - Default new providers and legacy entries lacking api_mode to
      chat_completions (only persisted on user save).
    - Deeplink imports now write api_mode: chat_completions explicitly
      instead of relying on URL heuristics; test renamed accordingly.
    - Rename the "Codex Responses (Copilot / OpenCode)" label to
      "OpenAI Responses" to match OpenAI's /v1/responses naming.
  • docs(readme): update SiliconFlow signup bonus to ¥16
    Sync the bonus credit amount across en/zh/ja README files to reflect
    the current SiliconFlow sponsor offer.
  • refactor(hermes): share provider-source marker constants and write guard
    After /simplify review of the P1-3 second wave, two small cleanups:
    
    - Lift the `_cc_source` / `providers_dict` magic strings out of
      ProviderCard into a shared helper (`isHermesReadOnlyProvider`) and
      named constants in hermesProviderPresets.ts. Front-end and back-end
      now document the same marker contract in two mirrored places
      instead of drifting strings.
    
    - Replace the duplicate `is_dict_only_provider` + `format!` branches
      at the top of `set_provider` / `remove_provider` with a single
      `ensure_provider_writable(config, name, verb)` guard. Future error
      copy tweaks only have to happen once.
    
    No behaviour change; all 52 hermes_config tests stay green.
  • feat(hermes): render providers: dict overlays as read-only cards
    ProviderCard now detects Hermes provider entries sourced from the
    v12+ `providers:` dict via the `_cc_source` marker that the backend
    injects, and renders a "Hermes Managed" badge beside the title.
    ProviderActions receives an `isReadOnly` prop that disables the Edit
    and Delete buttons (with a tooltip pointing the user at Hermes Web
    UI) while keeping Switch and Duplicate enabled — switching only
    touches `model.*`, and duplicate lets users fork the overlay into
    their own `custom_providers:` list.
    
    Three-locale i18n keys `provider.managedByHermes` /
    `provider.managedByHermesHint` added.
  • feat(hermes): surface providers: dict entries read-only
    Hermes v12+ migrated some provider entries from the `custom_providers:`
    list into a `providers:` dict (keyed by id). CC Switch previously
    ignored that source entirely, leaving users blind to providers they had
    configured via Hermes' own Web UI; the only feedback was a generic
    migration warning in the health banner.
    
    `get_providers()` now unions both sources, matching upstream
    `get_compatible_custom_providers` dedup order (list wins on name
    collision). Entries coming from the dict carry a `_cc_source =
    "providers_dict"` marker plus the original `provider_key`, which the
    UI layer will use to render them read-only. `set_provider` and
    `remove_provider` now refuse to touch dict-only entries, steering the
    user to Hermes Web UI. `sanitize_hermes_provider_keys` strips the UI
    markers on write so they never reach YAML.
    
    The `schema_migrated_v12` health warning copy reframes the situation:
    entries are shown read-only in CC Switch rather than invisible.
  • fix(hermes): prevent YAML pollution and drop of OAuth mcp auth
    DeepLink Hermes import was emitting camelCase (baseUrl / apiKey /
    apiMode) that the Hermes runtime does not recognise, poisoning
    `custom_providers:` entries on activation. The MCP sync path was
    also stripping `auth: oauth` on round-trip, silently downgrading
    OAuth-type servers to unauthenticated calls.
    
    The Hermes deeplink branch now emits snake_case via a dedicated
    builder; `sanitize_hermes_provider_keys` runs on both `set_provider`
    and `get_providers` so legacy DB records heal on next access.
    `HERMES_EXTRA_FIELDS` preserves `auth`. The `api_mode` dropdown gains
    `codex_responses` (Copilot / OpenCode), and the schema-migrated
    warning copy no longer hard-codes "v12" (upstream `_config_version`
    is now 19).
  • feat(hermes): memory enable switch + clearer migration warning copy
    Replaces the greyed-out "Memory is disabled" banner with a real Switch
    at the top of each memory tab. Users can now toggle Hermes' memory/user
    blobs without leaving CC Switch; the underlying write goes through the
    merge-aware `set_memory_enabled`, so budgets and external-provider
    settings survive toggle operations. The new `useToggleHermesMemoryEnabled`
    mutation invalidates the limits query so the Switch state and the
    amber disabled-hint update in lockstep.
    
    Reworks the `schema_migrated_v12` health banner copy to match the
    simplified "CC Switch only manages custom_providers" posture — it now
    tells users to reconcile migrated dict entries via Hermes Web UI,
    instead of the earlier (and now inaccurate) "CC Switch reads both".
  • feat(settings): add Hermes config dir override with data-driven dispatch
    Adds a dedicated Hermes row to the directory-override settings so users
    can point CC Switch at alternate Hermes config locations (e.g. a second
    profile directory for work/personal split). `get_config_dir` on the
    Rust side already supports hermes; this just wires up the frontend row.
    
    Wiring it through `useDirectorySettings` revealed a scaling problem:
    every supported app required five parallel ternary chains across
    `computeDefaultConfigDir`, `updateDirectory`, `browseDirectory`,
    `resetDirectory`, and `updateDirectoryState`. Replaces those with two
    lookup tables (`APP_DIRECTORY_META`, `DIRECTORY_KEY_TO_SETTINGS_FIELD`)
    so adding the next app is two entries, not fifteen edit sites.
    
    Drive-by cleanup from the same touch:
    * `resetAllDirectories` takes a `ResolvedAppDirectoryOverrides` object
      instead of five positional optional strings.
    * `setResolvedDirs` returns the same reference when the sanitized
      value is unchanged, so no-op edits don't cascade renders.
    
    Also lands all i18n updates for this series (`hermesConfigDir` and
    placeholder, Memory section's enable/disable/toggleFailed copy, and
    the reworded `schemaMigratedV12` warning) in zh/en/ja together.
  • refactor(hermes): simplify schema handling + preserve unknown provider fields
    Drops the v11→v12 providers-dict compat layer: CC Switch now only
    reads/writes `custom_providers:`, leaving migrated `providers:` dict
    entries to Hermes Web UI for reconciliation (Hermes' runtime already
    merges both shapes via `get_compatible_custom_providers`). The
    `schema_migrated_v12` health warning now points users there when a
    dict-migrated config is detected.
    
    Adds forward-compat merge to `set_provider`: when updating an existing
    entry, on-disk fields the UI payload didn't submit (e.g. Hermes-only
    `request_timeout_seconds`, `key_env`) are carried over. Without this,
    editing one field via CC Switch would silently strip the rest.
    
    Adds `set_memory_enabled` + `set_hermes_memory_enabled` Tauri command
    for the upcoming memory-switch UI. Writes go through a merge-aware
    section replacement so character budgets and external-provider fields
    survive toggle operations.
    
    Removes four dict-only helpers (`normalize_providers_dict_entry_for_read`,
    `rename_alias_key`, `json_obj_non_empty_str`,
    `resolve_provider_name_from_yaml_entry`) and the multi-section write
    helper. Simplifies `get_providers` / `remove_provider` / health scan
    back to list-only. Replaces nine obsolete dict-related tests with
    `set_provider_preserves_unknown_fields_on_update` and
    `set_memory_enabled_preserves_other_fields`.
  • feat(hermes): replace Prompts entry with Memory panel
    Hermes has no slash-prompt concept (templates live as Skills), so the
    Prompts tab for the Hermes app was always empty. Swap the toolbar Book
    button for a Brain button that opens a new Memory panel editing
    ~/.hermes/memories/{MEMORY,USER}.md — Hermes' first-class memory store
    which its Web UI exposes only as on/off toggles, never as an editor.
    
    The panel shows each file in its own tab with a character-budget bar
    read from config.yaml's nested memory.* section (memory_char_limit /
    user_char_limit, default 2200 / 1375). Edits are written atomically;
    Hermes picks them up on the next session start per MemoryStore.
    
    Also extract useDarkMode to src/hooks/useDarkMode.ts — the codebase
    already repeats the same MutationObserver pattern in 12+ places; this
    PR introduces the shared hook and uses it once, leaving the migration
    of the other copies to a follow-up.
  • refactor(hermes): delegate deep config to Hermes Web UI
    Slim the Hermes surface in CC Switch to match its core positioning —
    cross-client provider switching and shared MCP/prompts/skills — and
    delegate deep configuration (model, agent, env, skills, cron, logs)
    to the Hermes Web UI at http://127.0.0.1:9119.
    
    - Drop AgentPanel/EnvPanel/ModelPanel and their mutation commands,
      hooks, types, and i18n keys across zh/en/ja.
    - Add open_hermes_web_ui Tauri command that probes /api/status and
      launches the URL in the system browser. Hermes injects its own
      session token into the returned HTML, so CC Switch doesn't need
      to touch auth.
    - Surface the launcher from the Hermes toolbar and the health banner
      via a shared useOpenHermesWebUI() hook; the offline error code is
      defined once per side and referenced across the contract.
    - Keep read-only access to model.provider so ProviderList can still
      highlight the active supplier; apply_switch_defaults continues to
      write the top-level model section when switching providers.
    
    Net diff: +152 / -1253.
  • fix(presets): refresh stale context windows for DeepSeek and Claude 1M
    - DeepSeek V3.2 / R1 (Hermes, OpenClaw): 64K → 128K context
    - DeepSeek R1 max output: 8K → 64K (includes CoT tokens)
    - Claude Opus 4.7 / Sonnet 4.6 via OpenRouter: 200K → 1M context
  • fix(presets): refresh stale model IDs and backfill Hermes model lists
    - Bump NewAPI universal preset to Claude 4.7 / Sonnet 4.6 / Haiku 4.5 and
      Gemini 3.1; fix opusModel mistakenly pointing to Sonnet
    - Bump Gemini Native (Claude preset) to gemini-3.1-pro / gemini-3-flash
    - Bump TheRouter Gemini preset to gemini-3.1-pro
    - Backfill models[] + suggestedDefaults for 15 Hermes anthropic_messages
      presets:
        * Bailian For Coding: qwen3-coder-plus / qwen3-max
        * Kimi For Coding: kimi-for-coding
        * 13 third-party Claude proxies: claude-opus-4-7 / sonnet-4-6 /
          haiku-4-5-20251001
    - Add Claude Haiku 4.5 entry to Hermes OpenRouter model list
  • feat(hermes): switch eligible presets to chat_completions + GPT-5.4
    Migrate 18 Hermes provider presets from anthropic_messages to
    chat_completions to sidestep known upstream Hermes bugs (model-name
    dot-mangling in normalize_model_name, api_mode drop after v11->v12
    migration, and auxiliary_client OpenAI hardcode).
    
    Native providers now target each vendor's official OpenAI-compatible
    endpoint with correct model IDs: Kimi (kimi-k2.5-preview on /v1),
    Bailian (compatible-mode/v1 with Qwen3 defaults), Xiaomi MiMo, Longcat
    (/openai/v1), Zhipu GLM (/api/paas/v4), ModelScope, MiniMax, SiliconFlow,
    and Novita (/v3/openai).
    
    Aggregators (Shengsuanyun, AiHubMix, DMXAPI, Compshare, TheRouter)
    default to GPT-5.4 on chat_completions, mirroring the Codex preset
    lineup. TheRouter omits gpt-5.4-pro since that variant is Responses-only
    and Hermes implements only chat_completions. OpenRouter's existing
    openai/gpt-5 entry is bumped to openai/gpt-5.4.
    
    Claude-only proxies are left on anthropic_messages; their Codex
    counterparts use wire_api=responses, so there is no evidence their
    chat_completions endpoints serve OpenAI models.
  • chore(hermes): prune unused official presets and fix Nous endpoint
    Remove the Anthropic, OpenAI, and Google AI presets from the Hermes
    preset list. They were placeholder samples introduced when the Hermes
    module first landed and do not match the actual user paths in
    CC Switch (Claude / Codex go through OAuth, Gemini Native is its own
    adapter), and the upstream endpoints are not reachable for most of
    the target users anyway.
    
    Fix the Nous Research preset: its base_url was a fabricated domain
    (inference.nous.hermes.dev) that has never resolved. Point it at the
    real Nous Portal endpoint (inference-api.nousresearch.com/v1) and
    add apiKeyUrl so users can jump straight to portal.nousresearch.com
    to provision a key.
    
    Drop the now-orphan providerForm.presets.{anthropic,openai,googleai}
    i18n keys from zh / en / ja since no preset references them anymore.
  • feat(presets): sync Claude provider presets to Hermes
    Import 38 Claude presets into Hermes by mapping env-style
    ANTHROPIC_BASE_URL/AUTH_TOKEN to flat base_url/api_key, deriving
    api_mode from apiFormat (anthropic_messages or chat_completions),
    deduping ANTHROPIC_*_MODEL into models[], and pointing
    suggestedDefaults at ANTHROPIC_MODEL. Skip OAuth-only presets
    (Codex, Copilot), Bedrock SigV4, Gemini Native, and the three
    already shipped on the Hermes side (OpenRouter, Anthropic,
    DeepSeek). Place Shengsuanyun at the head of the Hermes array so
    the partner shows first in the preset panel.
    
    In the Claude preset list, restore Shengsuanyun back ahead of
    Gemini Native. The Gemini Native preset (#1918) was inserted
    between Claude Official and Shengsuanyun, which made the
    third_party category register first in the reduce-based grouping
    and pushed the aggregator block (and Shengsuanyun) behind it.
    
    Backfill the missing providerForm.presets translations across zh,
    en, and ja (openrouter, anthropic, openai, googleai, deepseek,
    together; plus shengsuanyun for en and ja) so existing Hermes
    preset names no longer render literal i18n keys.
  • fix(hermes): show active provider and wire add/enable/remove actions
    Switching a Hermes provider previously only fired a toast because the frontend treated Hermes as non-additive (unlike backend AppType::is_additive_mode, which lists OpenCode | OpenClaw | Hermes) and relied on the unused is_current DB flag for highlighting. Align the UI model with the backend:
    
    - Include Hermes in ProviderActions' isAdditiveMode so the main button switches between "Add" and "Remove".
    - Drive the "current" highlight from model.provider (via useHermesModelConfig) instead of the DB is_current field; model.provider is Hermes's real SSOT for the active provider.
    - Reuse OpenClaw's set-as-default button slot to expose an "Enable" action on Hermes that calls switchProvider, so providers already in config can be activated without re-adding. switch_normal + apply_switch_defaults already atomically update custom_providers and model.provider, so no backend change is needed.
    - Invalidate liveProviderIds + modelConfig + health in parallel after add/update/delete/switch via a new invalidateHermesProviderCaches helper, replacing four copies of three sequential awaits.
  • fix(hermes): persist providers under custom_providers so api_mode/model survive
    Writing to the v12+ `providers:` dict broke every anthropic_messages
    provider. Hermes `runtime_provider.py::_get_named_custom_provider` has a
    bug in its `providers:` branch: the returned entry drops `api_mode`,
    `transport`, `models`, and singular `model:`, and
    `_resolve_named_custom_runtime` then falls back to `chat_completions` —
    so an Anthropic-format endpoint receives OpenAI-format requests and
    returns 404.
    
    Keep using the legacy `custom_providers:` list; its normalization path
    (`_normalize_custom_provider_entry`) preserves every field. In addition,
    write a singular `model:` alongside the plural `models:` dict so the
    Hermes runtime and `/model` picker see the default model id.
    
    Also keep the `apply_switch_defaults` fix from the prior attempt:
    `model.provider` is always updated, and `model.default` is only
    overwritten when the new provider declares at least one model — so
    switching to an incomplete provider no longer silently no-ops.
  • feat(hermes): add API mode dropdown and per-provider model editor in form
    The Hermes provider form previously only exposed Base URL and API Key,
    forcing users to drop into the Model panel to hand-edit model IDs after
    adding a provider. Following OpenClaw's shape, the form now carries:
    
    - An API Mode selector (auto-detect / chat_completions / anthropic_messages).
      "auto" is a UI-only sentinel — selecting it deletes api_mode from the
      config so the YAML doesn't leak a redundant field.
    - A model list editor where the first row is badged as the default and
      each row has a collapsible Advanced panel for context_length and
      max_tokens. Adding/removing rows uses a UUID-keyed ref so typing in
      one input doesn't drop focus when another row is added.
    - A Fetch Models button that pulls /v1/models from the configured
      endpoint and exposes the catalog in a per-row dropdown, identical to
      OpenClaw's flow. The vendor grouping is memoized so keystrokes don't
      trigger a reduce+sort per model row — Radix DropdownMenuContent does
      not lazy-mount, so the inner JSX evaluates on every render regardless
      of whether the menu is open.
    
    Three-locale i18n keys are added together (zh/en/ja).
  • feat(hermes): bind per-provider models to top-level model: on switch
    Hermes custom_providers entries now carry an ordered models array
    (id / context_length / max_tokens) plus suggestedDefaults. The backend
    serializes the array to the YAML dict shape Hermes expects on write and
    inverts it on read, preserving insertion order via the preserve_order
    feature on serde_json.
    
    When a user switches providers, switch_normal calls apply_switch_defaults
    so the top-level model.default / model.provider follow the selected
    provider's first model. Previously switching a Hermes provider only
    shuffled custom_providers[] and left Hermes pointing at whatever
    model.provider was set before.
    
    Seven existing Hermes presets now ship with a curated models list so
    switching lands on a working default without a detour through the
    Model panel.
  • feat(copilot): strip thinking blocks before forwarding to save premium quota
    Copilot routes through OpenAI-compatible endpoints that reject Anthropic's
    thinking and redacted_thinking blocks. Previously the request would fail
    upstream, burning one premium interaction, and only then trigger
    thinking_rectifier to retry. This adds a proactive strip_thinking_blocks
    pass in the Copilot optimization pipeline (step 3.5, after tool_result
    merging). Signature fields and top-level thinking are left alone — those
    are the reactive rectifier's job on the error path.
    
    Also fixes a default-value inconsistency where CopilotOptimizerConfig's
    Default impl used "gpt-4o-mini" while the serde default function returned
    "gpt-5-mini" (aligned to gpt-5-mini, matching the reference implementation).
    
    Aligned with yuegongzi/copilot-api's /v1/messages handler behavior.