openclaw - 💡(How to fix) Fix [Feature]: Dashboard sessions with status "done" disappear from Control UI session list

Summary

Describe the feature

When a dashboard session (e.g., a research session created via Control UI) finishes its last reply, its status is set to done. The session then disappears from the Control UI session list, even though the user expects it to remain visible — just like any messaging app keeps completed conversations in the list.

Problem to solve

Use case

• I create a named dashboard session like "xxx".
• I do research in it over multiple back-and-forths.
• At the end of the day, I say "Let's continue tomorrow", and the session goes to done.
• Next morning, the session is gone from the sidebar. I have to ask my agent to manually edit sessions.json to change its status back to running just to see it again.

Expected behavior

• Sessions with status done should still appear in the Control UI session list (maybe greyed out or with a "completed" badge).
• Users should be able to reopen/continue a done session without CLI/API workarounds.

Proposed solution

Suggested solution

Option A: Always show all sessions in the list, with a visual indicator for status (running / done). Option B: Add a toggle/filter in the UI: "Show completed sessions". Option C: Keep done sessions visible by default; let session maintenance/pruning handle cleanup after a configurable TTL.

Alternatives considered

No response

Impact

Impact

• **Affected: All Control UI / WebChat users who create named dashboard sessions for long-running research or project work.
• **Severity: Moderately annoying; does not block core functionality (data is not lost) but forces users into CLI workarounds or contacting their agent to restore session visibility.
• **Frequency: Always — every time a dashboard session completes its last reply, the session disappears from the UI.
• **Consequence: Users lose visual access to their session list overnight or after a session ends. Recovery requires manually editing sessions.json or asking the agent to patch the status, which is neither discoverable nor user-friendly. This undermines the purpose of named sessions as persistent research containers.

Evidence/examples

No response

Additional information

No response