Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feature]: Cross-session management across gateways and mediums [1 comments, 2 participants]

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…
GitHub stats
NousResearch/hermes-agent#17193•Fetched 2026-04-29 06:36:49
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
StarrWulfeStarrWulfe
Participants
alt-glitchalt-glitchStarrWulfeStarrWulfe
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Problem or Use Case

Hermes Agent sessions are not consistently managed across different gateways and access mediums (Web UI / TUI / Telegram / Matrix / etc.). Users face several issues:

  1. No /sessions command in Telegram — Users cannot list or switch between existing sessions. Only /new (fresh session) and /resume [name] (requires a pre-named session) exist.

  2. No cross-medium session visibility — A session created in the Web UI is invisible from Telegram. There is no unified view of all sessions across all platforms.

  3. Session IDs are not human-readable — Sessions use UUIDs (e.g. 08082151-7682-4fee-b479-c97261d81a07). Users cannot correlate a session ID from one medium with a conversation in another.

  4. No way to recover untitled sessions — /resume [name] only works for named sessions. Untitled sessions are effectively invisible once you leave that medium.

Proposed Solution

  1. Add a /sessions command (all gateway platforms) that lists recent sessions with:

    • Session ID (or short hash)
    • Title (or first-message preview if untitled)
    • Platform origin (telegram / web / tui / etc.)
    • Last activity timestamp
    • Inline keyboard to select and switch to any listed session

  2. Add a /switch <session-id> command to explicitly switch to a specific session.

  3. Ensure session context is preserved and continuous across all gateway platforms for a given authenticated user.

  4. Promote /title usage — sessions should be nameable from any medium, and named sessions should be accessible via /resume from all mediums.

Additional Context

Filed after a user needed to look up session 08082151-7682-4fee-b479-c97261d81a07 (created in the Web UI, untitled) from Telegram. Without a title, /resume could not find it. There is currently no way to list or switch sessions from Telegram at all.

I’m also aware of similar proposals like #8366 that also add this kind of functionality parity as well and thought I’d add my own voice to the conversation.

Alternatives Considered

  • Relying solely on /new and /resume — insufficient: users cannot discover unnamed sessions across mediums.
  • Platform-level automatic session continuity — already works per-medium, but lacks explicit cross-medium session management commands.

Feature Type

Gateway / messaging improvement

Scope

Small (single file, < 50 lines)

Contribution

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

Debug Report (optional)

extent analysis

TL;DR

Implement a unified session management system with a /sessions command to list and switch between sessions across all gateway platforms.

Guidance

  • Introduce a /sessions command that lists recent sessions with essential details such as session ID, title, platform origin, and last activity timestamp.
  • Develop a /switch <session-id> command to explicitly switch to a specific session, ensuring session context preservation across platforms.
  • Promote the use of the /title command to enable users to name sessions from any medium, making them accessible via /resume from all mediums.
  • Ensure that the new commands are implemented consistently across all gateway platforms, including Telegram, Web UI, TUI, and Matrix.

Example

No code snippet is provided as the issue does not contain sufficient technical details for a specific implementation.

Notes

The proposed solution aims to address the inconsistencies in session management across different gateways and access mediums. However, the implementation details, such as the specific syntax and behavior of the new commands, are not specified in the issue.

Recommendation

Apply the proposed workaround by implementing the unified session management system with the /sessions and /switch commands, as it addresses the core issues of session visibility and management across different platforms.

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…
#retrieval issue#search optimization#API routing#API middleware#SSR setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING