Discord: it does not know how to attach files | Nous Research | Page 1

alpine garnet Apr 4, 2026, 3:24 PM

#

I’ve run into a situation many times where if I want a media attached to a message (a generated image, or tts), Hermes-agent will often write “MEDIA: /path/to/the/file” rather then attaching the media.
Usually instruct my instances to use the CLI I as a workaround but it feels meh, and would prefer to not have to do it haha.

Running on a random commit from yesterday, using codex gpt5.1 mini. It was already the case in v0.5 so not a regression as far as i can tell

Let me know if there’s anything I can provide to help

silk escarp Apr 5, 2026, 12:03 AM

#

This looks like a real gateway bug, not the model "not knowing" how to attach files.

Discord does have native attachment code for images, voice, video, and documents. Hermes also has a normal post-processing step that extracts MEDIA:/path/... and local file paths before sending the final message. The likely bad path here is streaming: the stream consumer edits raw text chunks directly, and it does not strip MEDIA: directives before they become visible.

So the practical workaround right now is to turn gateway streaming off:

In config:
streaming:
enabled: false
and restart the gateway.

What would help confirm it:

whether you have streaming.enabled: true
gateway logs around the failed turn, especially any of:

Post-stream media delivery failed
Failed to send media
extract_media
already_sent

alpine garnet Apr 5, 2026, 2:06 AM

#

Hey @silk escarp thanks so much for taking some tine to help!

I do have streaming->enabled set to false already, I didn't even know it was off haha.

I'll try to reproduce in a new session, capture the logs and session log

silk escarp Apr 5, 2026, 2:06 AM

#

awesome, thanks!

silk escarp Apr 5, 2026, 2:23 AM

#

sometimes i read deleted messages... hehe.
Yeah, that dump is a different problem.

That is not the Discord media-attach path failing. That session entry shows the model getting stuck in planning text and never actually producing the tool call it meant to make.

alpine garnet Apr 5, 2026, 2:24 AM

#

haha... I realized I was off topic 🙂 I try my best but can't reproduce

silk escarp Apr 5, 2026, 2:24 AM

#

cool. i also wonder if it's just the older mini model kinda messing up

alpine garnet Apr 5, 2026, 2:24 AM

#

The other issue I do have regularly too ~ I usually say "continue" and it manages to go on

#

Yeah I'm just being cheap haha

silk escarp Apr 5, 2026, 2:25 AM

#

what's this other issue? sorry, i cut you off

alpine garnet Apr 5, 2026, 2:26 AM

#

When hermes/the discord bot answers with some form of internal thinking about tool call rather than doing the tool call

silk escarp Apr 5, 2026, 2:26 AM

#

ah, like the deleted log message.

alpine garnet Apr 5, 2026, 2:26 AM

#

yep

#

I do have that semi regularly, I've been wondering if it's due to me using gpt5.1-mini

silk escarp Apr 5, 2026, 2:30 AM

#

i kinda wonder if sometimes during session compaction if the instruction to not respond occasionally gets stuck in the compressed message, but i need to dig into that further. i've ran into something similar once, but i'm not able to reliably repro it. basically, there's an instruction that says to compact and stuff and not emit a response... if that somehow becomes pinned in the session, it can be like fighting a system instruction. it's just a working theory rn for me. starting a new session if you run into it should clear it up. but it would be good to have logs of that as well.

#

and yeah... these mini models can have a bit more quirks than the larger ones.

iron blade Apr 6, 2026, 2:29 AM

#

@alpine garnet it should be fixed now, can you test

#Discord: it does not know how to attach files