hermes - 💡(How to fix) Fix [Bug]: Email gateway: Lack of subject-based session isolation and excessive notification volume [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…

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

Code Example

/debug command i sent using email - did not work, no reply

---
RAW_BUFFERClick to expand / collapse

Bug Description

The email gateway currently fails to isolate sessions based on the email subject line. When a user sends a message with a new subject while a task is already running, Hermes interrupts the current task instead of treating the new subject as a separate, isolated session. This behavior makes the email gateway difficult to use for concurrent or context-switching tasks.

Additionally, the gateway produces an overwhelming amount of notification noise. For a single user request, Hermes may send 100–200 emails containing redundant status updates such as "still working..." or "looking...".

Steps to Reproduce

  1. Configure and start the Hermes agent with the email gateway enabled.
  2. Send an email to the agent with Subject A containing a long-running task (e.g., "Research and summarize the history of LLMs").
  3. While the agent is processing, send a second email with Subject B containing a different query.
  4. Observe that the agent interrupts the task from Subject A to handle Subject B.
  5. Monitor the inbox during the process to observe the high volume of status update emails.

Expected Behavior

  1. Session Isolation: Each unique email subject should be treated as an isolated session. A message with a new subject should not interrupt a task running under a different subject.
  2. Notification Throttling: Status updates (e.g., "still working") should be batched, throttled, or sent only upon significant milestones to prevent inbox flooding.

Actual Behavior

  1. Task Interruption: Any incoming email from the same sender appears to hijack the current active session regardless of the subject line.
  2. Email Spam: The user receives 100–200 redundant emails for a single interaction, making the gateway nearly unusable due to the volume of "useless" info.

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

No response

Debug Report

/debug command i sent using email - did not work, no reply

Operating System

linux

Python Version

3.11.15

Hermes Version

0.10.40 (sent email with /version)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

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

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

hermes - 💡(How to fix) Fix [Bug]: Email gateway: Lack of subject-based session isolation and excessive notification volume [1 pull requests]