UPDATES • OpenClaw quick fix
Featured: @techSage

Session stuck ‘In progress’? Check terminal cleanup first.

A fresh OpenClaw gateway commit points to a subtle failure mode: a session can be finished while the active-run projection still makes it look stuck `In progress`. Do not start by killing random processes or deleting state. Treat it as a terminal-lifecycle cleanup problem: capture the symptom, check whether the task actually ended, update to a build that includes the fix when available, and keep retry/abort safety separate from the UI's active-session view.

In simple words: Make a safe copy if the step could change your setup, try the smallest check, then confirm OpenClaw is back to normal before doing more. The source link and commands stay below for people who want the technical detail.

Checklist
Confirm the visible symptom: `sessions.list` or the UI still shows an old run as active after the terminal/session already reached a final state.
Before cleanup, write down the session id, last terminal event, and whether retry/abort controls are still protecting a real in-flight run.
Triage note before deleting state
- Session id shown as active:
- Last visible terminal/state event:
- Is any process still running, or only the UI/list projection?
- OpenClaw version/commit:
- Rollback or backup label before upgrade/restart:
Update only after a verified backup or rollback note, then check the release/commit notes for the active-run cleanup fix before assuming local state is corrupt.
After update or restart, run one tiny session to completion and confirm the active list clears while retry/abort behavior still works for a genuinely running task.
Tiny post-fix smoke test
openclaw --version
# Run one low-risk session/task to completion.
# Then inspect your normal session list/UI and confirm the completed run is no longer shown as active.
If the stale run remains, preserve logs and avoid broad state deletion; narrow the report to gateway active-run projection versus actual session completion.
Success looks like
Completed sessions no longer stay visible as active `In progress` runs.
Retry/abort guard state is not confused with the user-facing active-run list.
Any remaining stuck-session report includes a version, session id, terminal event, and rollback label instead of a destructive cleanup guess.

Source: OpenClaw gateway commit + X field signal · link