Can I still use other sessions besides the main one?

Yes, other sessions like Feishu DMs or any newly created sessions usually work fine. The bug is specific to the main session's UI rendering in version 2026.3.12.

Will downgrading affect my other sessions?

No, downgrading OpenClaw to version 2026.3.11 should only affect the client-side Control UI and won't impact your other sessions or gateway configurations.

What if I don't know where the session state file is?

Check your OpenClaw gateway configuration files or logs for clues about data storage locations. The file is usually named something related to 'session-state' or the session ID.

Fix: OpenClaw Control UI Error Triangle on Main Session

TL;DR — Quick Fix

Downgrade OpenClaw to 2026.3.11 or reset the main session's persisted state to fix the error triangle and missing input box in the Control UI.

Run Diagnostics

Next Step

Fix now, then reduce repeat incidents

If this issue keeps coming back, validate your setup in Doctor first, then harden your config.

Open Doctor Harden Config

Error Signal

Control UI shows error triangleno input box when switching to main session

What's Happening

When you switch to the main session in the OpenClaw Control UI, you might see an error triangle and no input box. This makes the main session unusable from the web UI. This issue specifically started appearing in OpenClaw version 2026.3.12.

The Fix

The quickest way to get back to using your main session is to either:

Downgrade OpenClaw: Roll back to the previous stable version. Run this command in your terminal:
```
npm install -g [email protected]
```
Reset Main Session State: If you can't downgrade, you can reset the persisted state for your main session. Warning: This will delete your main session's chat history. On the gateway host, find and delete the persisted session state file for your main session. The exact location depends on your setup, but it's often within the OpenClaw data directory. After deleting the file, restart the OpenClaw gateway. You might need to consult your specific gateway configuration or logs to pinpoint the file.

As a temporary workaround, you can create a new session using /new in a non-main session (like a Feishu DM) or from the Sessions panel to continue your work.

Why This Occurs

This behavior bug appears to be a regression introduced in the 2026.3.12 release of the Control UI. It affects how the main session's state is loaded and rendered, leading to the error triangle and lack of an input field. The gateway logs show normal WebSocket disconnects and reconnects (code=1001) without specific errors, indicating a front-end or state management issue within the Control UI itself.

Prevention

Avoid upgrading to the latest pre-release or patch versions immediately after release. Always check the OpenClaw GitHub issues page for known regressions before applying updates, especially for critical components like the Control UI. If possible, test new versions in a non-production environment first. Reviewing changelogs for potential UI-related changes can also help anticipate such issues.

Last Updated: March 2026

Did this guide solve your problem?