openclaw - 💡(How to fix) Fix [Feature]: feat(control-ui): auto-name new sessions with timestamp 内容: [1 pull requests]

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…

Control UI new sessions should auto-name with creation timestamp for easy identification

Root Cause

Control UI new sessions should auto-name with creation timestamp for easy identification

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Summary

Control UI new sessions should auto-name with creation timestamp for easy identification

Problem to solve

In Control UI WebChat, typing /NEW creates a fresh dashboard session tab with a generic name. When multiple sessions are open, there's no quick way to tell which tab is which — users have to click through each tab to find the right conversation. This is especially inconvenient when switching back and forth between several active sessions.

Proposed solution

Auto-name new sessions with the time they were created. Format suggestions:

Same day: 14:12 Different day: 05-24 14:12 This would allow users to instantly distinguish sessions at a glance without clicking into each one.

Alternatives considered

Manual renaming would require new UI controls and user action every time. Timestamp auto-naming is zero-effort and universally useful. A config option for naming format would be even better but the simple default is already a big improvement.

Impact

Affected: All Control UI users who open multiple sessions Severity: Low (workflow friction, not blocking) Frequency: Every time /NEW is used (multiple times daily for power users) Consequence: Extra clicks to identify the right session tab

Evidence/examples

This is a common UX pattern — most chat apps (Slack, Discord, Telegram) show timestamps on conversations. The current Control UI session tabs lack any identifying metadata.

Additional information

The timestamp should respect the user's browser locale/timezone.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING