Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix feat: allow reference_image_urls in video_gen to accept filesystem paths in addition to HTTP URLs

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…
RAW_BUFFERClick to expand / collapse

Problem

The reference_image_urls parameter in VideoGenProvider.generate() requires HTTP/HTTPS URLs. Local filesystem paths are not accepted. This forces implementors to mirror reference images to a CDN before each generation call, adding latency and complexity.

Proposed Change

Accept file:// scheme or bare absolute paths in reference_image_urls, with automatic base64 encoding or upload handled by the Hermes plugin runtime before forwarding to the provider.

Motivation

Mother mirrors brand reference images to Tigris CDN (30-second SLA) before each Luma video generation specifically to satisfy this requirement. Filesystem path support would remove that step and reduce generation latency.

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 feat: allow reference_image_urls in video_gen to accept filesystem paths in addition to HTTP URLs