Skip to content

[Feature]: Telegram: After /new or /reset, automatically output the previous session title (or ID) for easy /resume #4528

@kamjin3086

Description

@kamjin3086

Problem or Use Case

When using Hermes via Telegram, users often run /new (or /reset) in a topic to start a fresh task that should not be influenced by previous context.

After the reset, the old session is detached from the current topic. Recovering it later requires going to the CLI (hermes sessions list) or remembering/guessing the exact title. This creates a fragmented experience, especially on mobile.

Proposed Solution

Minimal Change, High Value
After /new or /reset successfully creates a new session, automatically reply with something like:

✅ New session started.

Previous session title: coding-2026-04-02-projectX
Session ID: 20260402_103512_abc123

You can resume the previous conversation anytime with:
/resume coding-2026-04-02-projectX

This way, users can simply copy-paste the title (or ID) later to resume the old session directly in Telegram using /resume.

Alternatives Considered

A longer-term improvement could be adding /sessions command that shows a clickable list of recent sessions (with inline buttons to resume), but the above suggestion is much simpler and already solves most of the daily pain.

Use Case

  • Fixed topics like "Coding", "Research", "Projects".
  • Finish one task → /new → get the old title automatically → start new independent task.
  • Later want to continue the old one → just paste /resume old-title.

Why this is better

  • Extremely small code change (just print the previous session's title/ID right after reset).
  • Much more user-friendly than forcing everyone to switch to CLI.
  • Encourages good habits: users get a clear, copyable reference every time they reset.
  • Works perfectly with the existing /title and /resume commands.
  • No need for complex lists or inline keyboards initially.

This small enhancement would significantly improve the Telegram experience with almost zero added complexity.

Feature Type

Gateway / messaging improvement

Scope

Small (single file, < 50 lines)

Contribution

  • I'd like to implement this myself and submit a PR

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions