Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Make Discord voice inactivity timeout configurable [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#17790•Fetched 2026-05-01 05:55:47
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
danehapanadanehapana
Participants
alt-glitchalt-glitchdanehapanadanehapana
Timeline (top)
labeled ×4commented ×1

Fix Action

Fix / Workaround

Motivation

The Discord adapter currently has a hardcoded voice inactivity timeout (VOICE_TIMEOUT = 300), so Hermes leaves a voice channel after 5 minutes of inactivity. For persistent voice workflows, this is too aggressive and requires maintaining a local patch.

Why this should be configurable by design

Some Discord deployments use Hermes like a standing voice assistant in a server. In that mode, auto-leaving after 5 minutes breaks the workflow, but disabling/extending the timeout should not require patching gateway/platforms/discord.py.

Code Example

gateway:
  platforms:
    discord:
      voice_timeout_seconds: 0

---

HERMES_DISCORD_VOICE_TIMEOUT_SECONDS=0
RAW_BUFFERClick to expand / collapse

Feature description

Make the Discord voice-channel inactivity timeout configurable.

Motivation

The Discord adapter currently has a hardcoded voice inactivity timeout (VOICE_TIMEOUT = 300), so Hermes leaves a voice channel after 5 minutes of inactivity. For persistent voice workflows, this is too aggressive and requires maintaining a local patch.

Proposed solution

Add a config/env setting such as:

gateway:
  platforms:
    discord:
      voice_timeout_seconds: 0

and/or:

HERMES_DISCORD_VOICE_TIMEOUT_SECONDS=0

Suggested behavior:

  • Default remains 300 seconds to preserve current behavior.
  • Positive integer sets the inactivity timeout in seconds.
  • 0 disables automatic voice-channel leave due to inactivity.
  • Invalid values fall back to the default and log a warning.

Why this should be configurable by design

Some Discord deployments use Hermes like a standing voice assistant in a server. In that mode, auto-leaving after 5 minutes breaks the workflow, but disabling/extending the timeout should not require patching gateway/platforms/discord.py.

extent analysis

TL;DR

To make the Discord voice-channel inactivity timeout configurable, add a voice_timeout_seconds setting to the Discord platform configuration.

Guidance

  • Introduce a new configuration option voice_timeout_seconds in the Discord platform settings, allowing users to customize the inactivity timeout.
  • Update the Discord adapter to read this configuration value and apply it to the voice channel inactivity timeout logic.
  • Set a default value of 300 seconds to preserve the current behavior and handle invalid values by logging a warning and falling back to the default.
  • Consider adding environment variable support, such as HERMES_DISCORD_VOICE_TIMEOUT_SECONDS, to provide an alternative configuration method.

Example

gateway:
  platforms:
    discord:
      voice_timeout_seconds: 600  # sets the timeout to 10 minutes

Notes

This solution assumes that the existing VOICE_TIMEOUT constant is used consistently throughout the codebase and can be replaced with the new configurable value.

Recommendation

Apply the proposed workaround by adding the voice_timeout_seconds configuration option to make the Discord voice-channel inactivity timeout configurable, allowing for more flexible and persistent voice workflows.

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…
#mixed precision#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING