openclaw / openclaw/openclaw-windows-node

[Bug] Windows Companion crashes when opening older sessions that work in browser Dashboard

Open
#1,414 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:crash-loop issue-rating: 🦪 silver shellfish P1
Dominant language
C#
Stars
2.1k
Forks
295
Avg merge
1d 6h
Merged PRs (30d)
99

Description

Summary

Windows Companion crashes when selecting certain older chat sessions from the session picker. The same sessions open successfully in the browser Dashboard against the same Gateway, so the session data and Gateway appear healthy and the failure seems isolated to the Windows Companion / WinUI client.

Environment

  • Windows Companion / Windows Hub: v2026.9.3
  • OpenClaw CLI / Gateway: v2026.9.4 (3a9d69d)
  • Gateway runtime: Node v24.19.0
  • Gateway URL: ws://127.0.0.1:18789
  • Gateway status: running, connectivity probe OK
  • Platform: Windows with OpenClaw Gateway running under WSL/systemd user service

Steps to reproduce

  1. Start the OpenClaw Gateway and connect Windows Companion.
  2. Open Chat in Windows Companion.
  3. Open the session selector at the bottom (currently showing Main session).
  4. Select one of the older sessions in the list (for example, older ragenius:... sessions).
  5. Windows Companion crashes.
  6. Open the browser Dashboard at http://127.0.0.1:18789/.
  7. Open the same older session there.

Actual behavior

Windows Companion crashes when the older session is selected.

Expected behavior

The session should open normally in Windows Companion, as it does in the browser Dashboard.

Additional observations

  • New/current chats work in Windows Companion.
  • The same older chats are readable in the browser Dashboard, which strongly suggests this is a Companion-side rendering/session-loading issue rather than corrupt Gateway/session data.
  • Gateway and CLI versions match (2026.9.4), and the Gateway is healthy.
  • This appeared after upgrading the OpenClaw Gateway/session environment from an older installation to 2026.9.4.

Please let me know what Windows Companion crash logs or diagnostic bundle would be most useful to attach.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the crash in Windows Companion v2026.9.3 with an older session, then collect the Windows Companion crash logs or diagnostic bundle requested in the issue. Compare the failing session with the same session in the browser Dashboard; done means older sessions open without crashing while current chats continue to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.