Summary

Add session titles/preview snippets in the Sessions sidebar, so users can distinguish old conversations without opening them one by one.

Problem to solve

Today the Sessions list mostly shows technical IDs/keys and timestamps. After using /new multiple times, users cannot quickly identify which session contains which topic. They must click sessions one by one to find context.

This is a frequent UX pain in daily usage, especially for users who split work across many short-lived sessions.

Proposed solution

In Control UI/WebChat session list:

1. Show a human-friendly title per session

   • Default: auto-generate from first user message (or first meaningful turn).
   • Keep existing key/id internally for routing/debug.

2. Show one-line preview snippet

   • Use last user/assistant text excerpt (configurable preference).
   • Truncate with ellipsis.

3. Allow rename (optional but preferred)

   • Manual rename from context menu.
   • Keep auto-title as fallback.

4. Search/filter by title/snippet

   • Quickly jump to a prior topic.

5. No behavior change to routing semantics

   • /new behavior remains unchanged (new context instance, old sessions still available).

Alternatives considered

• Keep external notes/index files (workaround): works but adds friction and maintenance burden.
• Click-through each session manually: too slow and error-prone for heavy users.

Impact

• Affected: users with many sessions (especially Telegram/Control UI workflows).
• Severity: Medium (not a hard blocker, but persistent productivity hit).
• Frequency: Daily.
• Consequence: extra context-switching time, wrong session picks, slower task continuation.

Evidence/examples

• Repro pattern:

  1. Start several tasks, use /new multiple times.
  2. Observe Sessions sidebar.
  3. Try to return to a specific prior topic.
  4. Need to open sessions one by one to find the right one.

• Related user confusion: users can’t easily tell “which old room is which topic” from sidebar alone.

Additional information

A lightweight implementation (title + snippet only) would already solve most of the pain and can be backward-compatible.