openclaw - 💡(How to fix) Fix Feature Request: Semantic session titles in WebChat session list

Problem

The WebChat (Control UI) session list displays raw internal session keys like agent:main:dashboard:236... as the session identifier. These are gateway routing IDs with no semantic meaning, making it hard to identify which conversation is which when browsing recent sessions.

In contrast, services like DeepSeek Chat automatically generate a descriptive title for each conversation (e.g., "Java code structure", "Bug investigation") based on the first few messages, and allow users to rename sessions.

Expected Behavior

1. Auto-derived titles: WebChat should display a lightweight, derived title for dashboard sessions, based on the first few messages or key topics.
2. User-renameable: Users should be able to rename a session from the session list panel.
3. Fallback: If no title can be derived, fall back to the current session key or a timestamp-based label.

Technical Notes

• sessions_list tool already has an includeDerivedTitles parameter, but it reads transcripts synchronously and can block the event loop (see issue #33463). A lighter approach could read only the first N characters of the first user+assistant turn.
• The Control UI already has a sessions.js panel rendering component where displayName is referenced but not populated for dashboard sessions.
• Performance concern: avoid full transcript reads for the session list endpoint.

Suggested Approach

1. Add a server-side endpoint or augment sessions.list GWS message to return a lightweight derived title per session (e.g., extract first 80 chars of the first user message).
2. The Control UI renders this derived title when available, falling back to the session key.
3. Optionally add a rename action that persists a custom label in the session store.

References

• DeepSeek Chat: auto-naming conversations by content
• OpenClaw issue #33463: includeDerivedTitles event loop blocking
• Session management docs: /concepts/session