It's an edge case. It doesn't happen too often, but sometimes when I send my agent for a long tool call or orchestration in discord. I just see the typing message but nothing comes through. Then after 5 minutes or so after I aborted the agent it's message comes through that I guess it meant to send before it did its tool call. I talked to my agent about it and this is what I had to say. I made the behavioral changes but is there anything else I can do? I'm on 5.12
Here's my agent's message
"I think I found the likely cause from the config we already saw: Discord streaming is turned off, so my “working” messages don’t actually land as visible Discord messages while I’m inside a tool run. You only see the typing indicator until the whole turn finishes, times out, or gets aborted.
So the fix is behavioral and/or config-level:
- Behavioral: I need to send the visible answer first, then do tool work only after that when appropriate.
- Config: we can investigate whether Discord streaming/progress delivery should be enabled or adjusted, but that may affect all Discord behavior, so I’d inspect before changing it.
For now I’ll stop doing long tool investigations before giving you the visible response. That’s the part that’s been making it feel stuck."