Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix [Bug]: claw migrate: model alias copied verbatim instead of resolved to API ID [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#16745•Fetched 2026-04-28 06:51:04
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
diek617diek617
Participants
diek617diek617vominh1919vominh1919
Timeline (top)
labeled ×4commented ×1cross-referenced ×1renamed ×1

hermes claw migrate copies the OpenClaw model setting verbatim as a display alias (e.g. "Claude Opus 4.6") into ~/.hermes/config.yaml, instead of resolving it to the corresponding Anthropic API model ID (claude-opus-4-6). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Workaround

After claw migrate, manually correct the model setting:

hermes config set model claude-opus-4-6

Or whichever API model ID the user wants. Verifying via hermes config show | grep -A 1 Model confirms the fix.

PR fix notes

PR #16778: fix: resolve model aliases during claw migrate (#16745)

Description (problem / solution / changelog)

Summary

hermes claw migrate copies the OpenClaw model setting verbatim as a display alias (e.g. "Claude Opus 4.6") into ~/.hermes/config.yaml, instead of resolving it to the actual API model ID (e.g. claude-opus-4-6). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

Root Cause

migrate_model_config() in openclaw_to_hermes.py reads agents.defaults.model and copies it directly. It never consults agents.defaults.models (plural) — the alias catalog that maps display names to API IDs. The catalog is only archived for manual review, never used for resolution.

Fix

After stripping the model string, look it up in the agents.defaults.models catalog:

  • If found with an "id" field, use the resolved API ID (prepending provider prefix if needed)
  • If found as a plain string, use that directly
  • If not found (already an API ID), pass through unchanged

File changed: optional-skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py (+16 lines)

Example

OpenClaw config:

{
  "agents": {
    "defaults": {
      "model": "Claude Opus 4.6",
      "models": {
        "Claude Opus 4.6": { "id": "claude-opus-4-6", "provider": "anthropic" }
      }
    }
  }
}

Before: Hermes config gets model: "Claude Opus 4.6" → API returns 404 After: Hermes config gets model: "anthropic/claude-opus-4-6" → works correctly

Fixes #16745

Changed files

  • optional-skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py (modified, +16/-0)

Code Example

model:
  default: Claude Opus 4.6

---

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

hermes config set model claude-opus-4-6

---

model:
  default: Claude Opus 4.6

---

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

hermes config set model claude-opus-4-6

---

model:
  default: Claude Opus 4.6

---

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

hermes config set model claude-opus-4-6

---

model:
  default: Claude Opus 4.6

---

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

---

hermes config set model claude-opus-4-6

---

claw migrate: model alias migrated as display string instead of resolved API ID

## Summary

`hermes claw migrate` copies the OpenClaw model setting verbatim as a display alias (e.g. `"Claude Opus 4.6"`) into `~/.hermes/config.yaml`, instead of resolving it to the corresponding Anthropic API model ID (`claude-opus-4-6`). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

## What I expected

`claw migrate` reads `openclaw.json` which maintains a two-level model definition — a display alias (e.g. `"Claude Opus 4.6"`) mapped to a fully-qualified API ID (e.g. `anthropic/claude-opus-4-6`). I expected the migration to write the resolved API ID into `config.yaml.model` so Hermes can call the API directly.

## What actually happens

The display alias is written verbatim. After migration, `config.yaml` contains:


model:
  default: Claude Opus 4.6


When Hermes makes an API call, it sends `Claude Opus 4-6` (with the period auto-rewritten to a hyphen, but spaces and capital letters preserved) as the model name. Anthropic's API responds:


API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6


## Reproduction


# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6


## Environment

- Hermes Agent v0.11.0 (2026.4.23)
- Python 3.11.15
- Source: a typical OpenClaw layout where `openclaw.json` defines models with both an alias display name and a fully-qualified API ID under `agents.defaults.models`

## Workaround

After `claw migrate`, manually correct the model setting:


hermes config set model claude-opus-4-6


Or whichever API model ID the user wants. Verifying via `hermes config show | grep -A 1 Model` confirms the fix.

## Suggested fix

When `claw migrate` encounters an OpenClaw model field that points to an alias rather than an API ID, it should resolve the alias by looking up the corresponding entry in `agents.defaults.models[*].alias` and writing the fully-qualified ID (or the bare API ID after stripping the `anthropic/` prefix) into `config.yaml.model`. Falling back to the alias unchanged should at least emit a warning, and the unresolved-alias case could be flagged in the migration summary so operators know to fix it manually.

---
RAW_BUFFERClick to expand / collapse

Bug Description

claw migrate: model alias migrated as display string instead of resolved API ID

Summary

hermes claw migrate copies the OpenClaw model setting verbatim as a display alias (e.g. "Claude Opus 4.6") into ~/.hermes/config.yaml, instead of resolving it to the corresponding Anthropic API model ID (claude-opus-4-6). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

What I expected

claw migrate reads openclaw.json which maintains a two-level model definition — a display alias (e.g. "Claude Opus 4.6") mapped to a fully-qualified API ID (e.g. anthropic/claude-opus-4-6). I expected the migration to write the resolved API ID into config.yaml.model so Hermes can call the API directly.

What actually happens

The display alias is written verbatim. After migration, config.yaml contains:

model:
  default: Claude Opus 4.6

When Hermes makes an API call, it sends Claude Opus 4-6 (with the period auto-rewritten to a hyphen, but spaces and capital letters preserved) as the model name. Anthropic's API responds:

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Reproduction

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Environment

  • Hermes Agent v0.11.0 (2026.4.23)
  • Python 3.11.15
  • Source: a typical OpenClaw layout where openclaw.json defines models with both an alias display name and a fully-qualified API ID under agents.defaults.models

Workaround

After claw migrate, manually correct the model setting:

hermes config set model claude-opus-4-6

Or whichever API model ID the user wants. Verifying via hermes config show | grep -A 1 Model confirms the fix.

Suggested fix

When claw migrate encounters an OpenClaw model field that points to an alias rather than an API ID, it should resolve the alias by looking up the corresponding entry in agents.defaults.models[*].alias and writing the fully-qualified ID (or the bare API ID after stripping the anthropic/ prefix) into config.yaml.model. Falling back to the alias unchanged should at least emit a warning, and the unresolved-alias case could be flagged in the migration summary so operators know to fix it manually.

Steps to Reproduce

claw migrate: model alias migrated as display string instead of resolved API ID

Summary

hermes claw migrate copies the OpenClaw model setting verbatim as a display alias (e.g. "Claude Opus 4.6") into ~/.hermes/config.yaml, instead of resolving it to the corresponding Anthropic API model ID (claude-opus-4-6). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

What I expected

claw migrate reads openclaw.json which maintains a two-level model definition — a display alias (e.g. "Claude Opus 4.6") mapped to a fully-qualified API ID (e.g. anthropic/claude-opus-4-6). I expected the migration to write the resolved API ID into config.yaml.model so Hermes can call the API directly.

What actually happens

The display alias is written verbatim. After migration, config.yaml contains:

model:
  default: Claude Opus 4.6

When Hermes makes an API call, it sends Claude Opus 4-6 (with the period auto-rewritten to a hyphen, but spaces and capital letters preserved) as the model name. Anthropic's API responds:

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Reproduction

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Environment

  • Hermes Agent v0.11.0 (2026.4.23)
  • Python 3.11.15
  • Source: a typical OpenClaw layout where openclaw.json defines models with both an alias display name and a fully-qualified API ID under agents.defaults.models

Workaround

After claw migrate, manually correct the model setting:

hermes config set model claude-opus-4-6

Or whichever API model ID the user wants. Verifying via hermes config show | grep -A 1 Model confirms the fix.

Suggested fix

When claw migrate encounters an OpenClaw model field that points to an alias rather than an API ID, it should resolve the alias by looking up the corresponding entry in agents.defaults.models[*].alias and writing the fully-qualified ID (or the bare API ID after stripping the anthropic/ prefix) into config.yaml.model. Falling back to the alias unchanged should at least emit a warning, and the unresolved-alias case could be flagged in the migration summary so operators know to fix it manually.

Expected Behavior

claw migrate: model alias migrated as display string instead of resolved API ID

Summary

hermes claw migrate copies the OpenClaw model setting verbatim as a display alias (e.g. "Claude Opus 4.6") into ~/.hermes/config.yaml, instead of resolving it to the corresponding Anthropic API model ID (claude-opus-4-6). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

What I expected

claw migrate reads openclaw.json which maintains a two-level model definition — a display alias (e.g. "Claude Opus 4.6") mapped to a fully-qualified API ID (e.g. anthropic/claude-opus-4-6). I expected the migration to write the resolved API ID into config.yaml.model so Hermes can call the API directly.

What actually happens

The display alias is written verbatim. After migration, config.yaml contains:

model:
  default: Claude Opus 4.6

When Hermes makes an API call, it sends Claude Opus 4-6 (with the period auto-rewritten to a hyphen, but spaces and capital letters preserved) as the model name. Anthropic's API responds:

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Reproduction

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Environment

  • Hermes Agent v0.11.0 (2026.4.23)
  • Python 3.11.15
  • Source: a typical OpenClaw layout where openclaw.json defines models with both an alias display name and a fully-qualified API ID under agents.defaults.models

Workaround

After claw migrate, manually correct the model setting:

hermes config set model claude-opus-4-6

Or whichever API model ID the user wants. Verifying via hermes config show | grep -A 1 Model confirms the fix.

Suggested fix

When claw migrate encounters an OpenClaw model field that points to an alias rather than an API ID, it should resolve the alias by looking up the corresponding entry in agents.defaults.models[*].alias and writing the fully-qualified ID (or the bare API ID after stripping the anthropic/ prefix) into config.yaml.model. Falling back to the alias unchanged should at least emit a warning, and the unresolved-alias case could be flagged in the migration summary so operators know to fix it manually. maxidijk@Mac craftbot-mail-triage %

Actual Behavior

claw migrate: model alias migrated as display string instead of resolved API ID

Summary

hermes claw migrate copies the OpenClaw model setting verbatim as a display alias (e.g. "Claude Opus 4.6") into ~/.hermes/config.yaml, instead of resolving it to the corresponding Anthropic API model ID (claude-opus-4-6). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

What I expected

claw migrate reads openclaw.json which maintains a two-level model definition — a display alias (e.g. "Claude Opus 4.6") mapped to a fully-qualified API ID (e.g. anthropic/claude-opus-4-6). I expected the migration to write the resolved API ID into config.yaml.model so Hermes can call the API directly.

What actually happens

The display alias is written verbatim. After migration, config.yaml contains:

model:
  default: Claude Opus 4.6

When Hermes makes an API call, it sends Claude Opus 4-6 (with the period auto-rewritten to a hyphen, but spaces and capital letters preserved) as the model name. Anthropic's API responds:

API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Reproduction

# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6

Environment

  • Hermes Agent v0.11.0 (2026.4.23)
  • Python 3.11.15
  • Source: a typical OpenClaw layout where openclaw.json defines models with both an alias display name and a fully-qualified API ID under agents.defaults.models

Workaround

After claw migrate, manually correct the model setting:

hermes config set model claude-opus-4-6

Or whichever API model ID the user wants. Verifying via hermes config show | grep -A 1 Model confirms the fix.

Suggested fix

When claw migrate encounters an OpenClaw model field that points to an alias rather than an API ID, it should resolve the alias by looking up the corresponding entry in agents.defaults.models[*].alias and writing the fully-qualified ID (or the bare API ID after stripping the anthropic/ prefix) into config.yaml.model. Falling back to the alias unchanged should at least emit a warning, and the unresolved-alias case could be flagged in the migration summary so operators know to fix it manually.

Affected Component

Setup / Installation

Messaging Platform (if gateway-related)

No response

Debug Report

claw migrate: model alias migrated as display string instead of resolved API ID

## Summary

`hermes claw migrate` copies the OpenClaw model setting verbatim as a display alias (e.g. `"Claude Opus 4.6"`) into `~/.hermes/config.yaml`, instead of resolving it to the corresponding Anthropic API model ID (`claude-opus-4-6`). Hermes then sends the alias as the model parameter to the Anthropic API, which responds with HTTP 404 model not found.

## What I expected

`claw migrate` reads `openclaw.json` which maintains a two-level model definition — a display alias (e.g. `"Claude Opus 4.6"`) mapped to a fully-qualified API ID (e.g. `anthropic/claude-opus-4-6`). I expected the migration to write the resolved API ID into `config.yaml.model` so Hermes can call the API directly.

## What actually happens

The display alias is written verbatim. After migration, `config.yaml` contains:


model:
  default: Claude Opus 4.6


When Hermes makes an API call, it sends `Claude Opus 4-6` (with the period auto-rewritten to a hyphen, but spaces and capital letters preserved) as the model name. Anthropic's API responds:


API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6


## Reproduction


# 1. Have an openclaw.json with an alias-style model definition
cat /data/.openclaw/openclaw.json | jq '.agents.defaults.models'
# {
#   "model": { "primary": "Claude Opus 4.6" },
#   "models": {
#     "anthropic/claude-opus-4-6": { "alias": "Claude Opus 4.6" }
#   }
# }

# 2. Run claw migrate
hermes claw migrate --source /data/.openclaw --preset full --overwrite --yes

# 3. Inspect the resulting config
grep -A 1 '^model:' ~/.hermes/config.yaml
# model:
#   default: Claude Opus 4.6     <-- alias copied verbatim, not resolved

# 4. Try a one-shot call
hermes --oneshot "ping"
# API call failed after 3 retries: HTTP 404: model: Claude Opus 4-6


## Environment

- Hermes Agent v0.11.0 (2026.4.23)
- Python 3.11.15
- Source: a typical OpenClaw layout where `openclaw.json` defines models with both an alias display name and a fully-qualified API ID under `agents.defaults.models`

## Workaround

After `claw migrate`, manually correct the model setting:


hermes config set model claude-opus-4-6


Or whichever API model ID the user wants. Verifying via `hermes config show | grep -A 1 Model` confirms the fix.

## Suggested fix

When `claw migrate` encounters an OpenClaw model field that points to an alias rather than an API ID, it should resolve the alias by looking up the corresponding entry in `agents.defaults.models[*].alias` and writing the fully-qualified ID (or the bare API ID after stripping the `anthropic/` prefix) into `config.yaml.model`. Falling back to the alias unchanged should at least emit a warning, and the unresolved-alias case could be flagged in the migration summary so operators know to fix it manually.

Operating System

Ubuntu 24.04

Python Version

No response

Hermes Version

No response

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

extent analysis

TL;DR

The issue can be fixed by manually correcting the model setting after running claw migrate or by modifying the claw migrate command to resolve the alias to the corresponding API ID.

Guidance

  • The claw migrate command is not resolving the model alias to the corresponding API ID, resulting in a 404 error when making API calls.
  • To fix this, you can manually correct the model setting using the command hermes config set model <api_id>.
  • Alternatively, you can modify the claw migrate command to resolve the alias by looking up the corresponding entry in agents.defaults.models[*].alias and writing the fully-qualified ID into config.yaml.model.
  • Verify the fix by running hermes config show | grep -A 1 Model and checking that the API ID is correctly set.

Example

hermes config set model claude-opus-4-6

This command sets the model to the correct API ID, which should resolve the 404 error.

Notes

  • The issue is specific to the claw migrate command and the way it handles model aliases.
  • The suggested fix requires modifying the claw migrate command or manually correcting the model setting after each migration.
  • It is recommended to submit a PR to fix this issue permanently.

Recommendation

Apply workaround: Manually correct the model setting after running claw migrate using the command hermes config set model <api_id>. This will ensure that the API ID is correctly set and the 404 error is resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#memory management#API rate limit#retriever error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - ✅(Solved) Fix [Bug]: claw migrate: model alias copied verbatim instead of resolved to API ID [1 pull requests, 1 comments, 2 participants]