openclaw - 💡(How to fix) Fix Telegram/chat surfaces: /sessions list + /resume <id> for past sessions

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…

Fix Action

Fix / Workaround

Workaround today

RAW_BUFFERClick to expand / collapse

Problem

On chat surfaces (Telegram in particular), /new archives the current session and starts a fresh one, but there's no in-chat way to see past sessions or resume one. Compare with claude code, where resume lists prior sessions and lets you pick one.

Today the only related primitive is /focus <target>, which binds the current chat to a session id — but you need to already know the id, and there's no list command on Telegram to find it. Session management effectively lives in the Control UI / dashboard, which is a context switch away from the surface you're chatting on.

Proposal

Add a /sessions (or /resume) text+native command on chat surfaces that:

  1. /sessions — lists the sender's recent sessions (id, last-active time, short title/first-message preview, model).
  2. /sessions resume <id> (or /resume <id>) — rebinds the current chat to that session id (effectively /focus <id> with discoverability).
  3. Native button menu on Telegram/Discord where supported, so it's a pick-list rather than typing an id.

Scope: per-sender, respects existing allowlists and session.identityLinks. Archived sessions included; pruned ones excluded.

Why

  • Parity with claude code resume UX — common request from users who jump between chat and CLI.
  • Reduces dashboard round-trips for a frequent operation.
  • Composes nicely with /dock-* for moving the resumed session's reply route.

Workaround today

/focus <id> if you happen to know the id (e.g. from /status or the dashboard). Not discoverable from Telegram.

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

openclaw - 💡(How to fix) Fix Telegram/chat surfaces: /sessions list + /resume <id> for past sessions