hermes - 💡(How to fix) Fix claw migrate produces api_mode: chat_completions for byoky-anthropic (should be anthropic_messages) [4 comments, 3 participants]

Summary

hermes claw migrate writes a custom_providers entry for the byoky-anthropic provider with api_mode: chat_completions, but byoky's bridge only proxies the native Anthropic shape on /v1/messages. The OpenAI-compat path /chat/completions returns 404, so a freshly migrated user hits a 404 the first time they run hermes.

Where it's wrong

optional-skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py:2098-2108

api_type = prov_cfg.get("apiType") or prov_cfg.get("type") or "openai"
api_mode_map = {
    "openai": "chat_completions",
    "anthropic": "anthropic_messages",
    "cohere": "chat_completions",
}
entry = {
    "name": prov_name,
    "base_url": prov_cfg["baseUrl"],
    "api_key": "",
    "api_mode": api_mode_map.get(api_type, "chat_completions"),
}

Two issues stack:

1. Field name mismatch. OpenClaw provider configs declare the wire shape as api: \"anthropic-messages\" (see e.g. byoky's official OpenClaw plugin: https://github.com/MichaelLod/byoky/blob/main/packages/openclaw-plugin/src/index.ts#L215). The migrator only checks apiType or type, never api, so api_type falls back to the default \"openai\".
2. Map key mismatch. Even if the migrator did read api, the value is \"anthropic-messages\" (hyphenated), but the lookup key is \"anthropic\". So it would still fall through to the default chat_completions.

Net result: any custom provider using the native Anthropic shape gets migrated as if it were OpenAI-compat, which 404s on the byoky bridge (and would silently use the wrong wire format anywhere else).

Reproduction

1. Install OpenClaw + the byoky openclaw plugin (openclaw plugins install @byoky/openclaw-plugin --dangerously-force-unsafe-install); this creates a byoky-anthropic provider in ~/.openclaw/openclaw.json with \"api\": \"anthropic-messages\", \"baseUrl\": \"http://127.0.0.1:19280/anthropic\".
2. Install Hermes, run hermes claw migrate.
3. Inspect ~/.hermes/config.yaml — the migrated custom_providers entry has api_mode: chat_completions.
4. Set model.provider: byoky-anthropic and run hermes chat -q ping. You get HTTP 404 from 127.0.0.1:19280/anthropic/chat/completions (the bridge only exposes /v1/messages).

Suggested fix

Read api as well, and add the hyphenated key:

api_type = (
    prov_cfg.get(\"apiType\")
    or prov_cfg.get(\"type\")
    or prov_cfg.get(\"api\")
    or \"openai\"
)
api_mode_map = {
    \"openai\": \"chat_completions\",
    \"anthropic\": \"anthropic_messages\",
    \"anthropic-messages\": \"anthropic_messages\",
    \"cohere\": \"chat_completions\",
}

Workaround for affected users

Edit ~/.hermes/config.yaml and flip api_mode for the migrated entry, or run byoky-bridge hermes-setup (shipped in @byoky/[email protected]) which does this idempotently.

Environment

• Hermes Agent v0.6.0 (2026.3.30)
• OpenClaw 2026.4.21
• @byoky/openclaw-plugin 0.9.5