Cairn

OpenClaw migration bugs and setup wizard fixes

NousResearch/hermes-agent · cluster 5685 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #13187. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #13187. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple issues and fixes related to the OpenClaw migration process, including stale provider/gateway checks, setup wizard skipping imported sections, and Windows onboarding getting stuck after migration. A few members touch adjacent desktop provider surfacing and unrelated salvaged bug fixes.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #13187 fix: salvage tier-1 bug fixes from PRs #7387, #9091, #6293, #13131

    merged to main

    files: cli.py, gateway/platforms/discord.py, gateway/platforms/telegram.py, hermes_cli/setup.py, scripts/release.py, tests/e2e/conftest.py, tests/e2e/test_discord_adapter.py, tests/hermes_cli/test_setup_openclaw_migration.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #13131 fix: update openclaw migration vars · merged via another change → #13187
  • #37357 fix(setup): detect custom provider key_env in provider readiness check (#37296) · done elsewhere → d682f32, #37296
Closed issues · 3
  • Closed#5685Setup wizard openclaw migration tests: setup_model_provider called when it shouldn't be
  • Closed#13025[Bug]: OpenClaw migration section summary uses stale/incomplete provider and gateway checks
  • Closed#37296Bug: Windows Desktop onboarding stays stuck with named custom provider after migration
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.25: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
apps/desktop
Merged PRs
#13187
Closed issues
3
Attempts
2 PRs closed without merging
Fix link checked
20 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/5685.json
cluster/5685.md