Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: Control UI session picker should show derived titles instead of session IDs

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The session dropdown in Control UI currently displays raw session keys like agent:main:dashboard:uuid, which makes it extremely difficult to navigate between conversations in daily use. Nobody remembers UUIDs, but users can almost always recall what topic they were discussing in each session.

The Gateway sessions.list RPC already supports includeDerivedTitles, which generates readable titles from conversation content. The frontend just needs to use it.

Root Cause

When using the control UI, displaying the session ID in the session dropdown is very user-unfriendly. As a user, I need to select different sessions from the dropdown to continue my original task. However, displaying the session ID in the session box causes me a lot of trouble because, based on those session IDs, I simply cannot recall what I discussed with OpenClaw in each session corresponding to that ID.

RAW_BUFFERClick to expand / collapse

Summary

The session dropdown in Control UI currently displays raw session keys like agent:main:dashboard:uuid, which makes it extremely difficult to navigate between conversations in daily use. Nobody remembers UUIDs, but users can almost always recall what topic they were discussing in each session.

The Gateway sessions.list RPC already supports includeDerivedTitles, which generates readable titles from conversation content. The frontend just needs to use it.

Problem to solve

The session dropdown in Control UI currently displays raw session keys like agent:main:dashboard:uuid, which makes it extremely difficult to navigate between conversations in daily use. Nobody remembers UUIDs, but users can almost always recall what topic they were discussing in each session.

The Gateway sessions.list RPC already supports includeDerivedTitles, which generates readable titles from conversation content. The frontend just needs to use it.

Proposed solution

  1. Call sessions.list with includeDerivedTitles: true
  2. Display derivedTitle in the session picker dropdown, fallback to session key
  3. Optionally: allow manual session renaming

Alternatives considered

No response

Impact

When using the control UI, displaying the session ID in the session dropdown is very user-unfriendly. As a user, I need to select different sessions from the dropdown to continue my original task. However, displaying the session ID in the session box causes me a lot of trouble because, based on those session IDs, I simply cannot recall what I discussed with OpenClaw in each session corresponding to that ID.

Evidence/examples

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING