openclaw - 💡(How to fix) Fix [Bug]: Dashboard session picker dropdown does not switch sessions — onSwitchSession is a no-op in chat view

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

In the Control UI Dashboard, clicking any session in the header session picker dropdown (or sidebar session list) closes the picker but does not switch to the selected session. The same v2026.5.27 version works correctly on another machine.

Root cause traced to dist/control-ui/assets/index-89Mm3xEP.js: the click handler in jA() calls n(e, r.key) to switch sessions, but n (onSwitchSession) defaults to () => void 0 (no-op). The actual session switch is never dispatched. WebSocket confirms only sessions.list fires on click — no chat.history or subscribe events.

Steps to reproduce

1. Open Control UI Dashboard (http://127.0.0.1:18789/)
2. Click the session picker in the top bar (next to "Main session")
3. Click any session other than the current one
4. Picker closes, view stays on current session

Expected behavior

Clicking a session in the picker should switch the dashboard view to that session's chat history.

Actual behavior

The picker closes, the current session view remains unchanged. No session switch occurs.

OpenClaw version

v2026.5.27 (27ae826), clean npm reinstall tested

Operating system

Windows 10 Pro 22H2 (19045)

Install method

No response

Model

deepseek/deepseek-v4-pro (current session), deepseek/deepseek-v4-flash (default)

Provider / routing chain

deepseek (primary), moonshot/kimi (search). WebChat → local Gateway (127.0.0.1:18789)

Additional provider/model setup details

Code path:

• eA() defaults onSwitchSession to () => void 0 (no-op)
• AA() passes it through to jA()
• jA() click handler: `@click=${()=>{pA(e), r.key!==e.sessionKey

Ruled out: data corruption (rebuilt sessions.json), browser ca

Workaround (DevTools Console):

document.querySelector('openclaw-app').sessionKey = 'target-sessio
document.querySelector('openclaw-app').requestUpdate();

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response