hermes - 💡(How to fix) Fix mcp_twitter download_tweet_video timeout too short for large videos (~77MB)

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…

Root Cause

Hermes Agent enforces a 120s timeout on all MCP server tool calls. Large HLS video download + ffmpeg merge takes longer than this limit.

RAW_BUFFERClick to expand / collapse

Problem

Config: mcp_servers.twitter.timeout: 120 (2 minutes)

Large HLS videos (~77MB, 88+ fragments) fail to download completely. The MCP tool gets killed at ~30% (exit code 130) while downloading.

Reproduction

  1. Tweet with ~77MB HLS video
  2. Call mcp_twitter_download_tweet_video
  3. Tool killed at ~30% progress (exit 130)
  4. Direct yt-dlp in terminal completes successfully (~5 min)

Root Cause

Hermes Agent enforces a 120s timeout on all MCP server tool calls. Large HLS video download + ffmpeg merge takes longer than this limit.

Expected Behavior

Either:

  1. Increase the default timeout for twitter MCP server (e.g. 600s for download tools)
  2. Add per-tool timeout override in config
  3. Document the timeout limitation for large file downloads

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