Works in the TUI, not in Telegram.
#notify_on_complete not ping Telegram channel
iron basin
edgy socket
That should work in Telegram too, so this is not an expected Telegram limitation.
notify_on_complete is wired through the gateway watcher path, so if the background process finished and no completion message came back to the Telegram chat, that points to the gateway-side watcher/notification flow not firing correctly for that session.
Please send:
/debug
the relevant gateway.log lines from when you start the background command until a few seconds after it exits
and your display.background_process_notifications setting if you changed it
Your simple sleep 5 && echo "Done!" repro is good, so that should be enough to see whether the watcher was registered and whether the completion notification was ever queued back to Telegram.
iron basin
edgy socket
That TUI screenshot helps a lot — it means notify_on_complete itself is working, and the problem is specifically in the Telegram gateway path.
Please send:
/debug
the relevant gateway.log lines from when you start the background command until a few seconds after it exits
and whether you changed display.background_process_notifications from its default
Your sleep 5 && echo "Done!" test is perfect for this. What we need to see now is whether the watcher got registered and whether the completion event was actually queued back to Telegram.
iron basin
background_process_notifications: all
Oddly, the gateway logs cut off after April 11th, so they aren't very helpful.
edgy socket
If gateway.log is stale, use agent.log instead.
Hermes writes everything to agent.log, and gateway.log is just a gateway-only side log, so for this issue the useful ask is the agent.log lines from when you start the background command until a few seconds after it exits.
Please send:
/debug
the relevant agent.log lines for your sleep 5 && echo "Done!" test
and confirm whether you started the gateway under systemd
What we need to see now is whether the watcher got registered in the process registry and whether the completion event was ever queued back to Telegram.
iron basin
Logs not showing anything related. No errors, nothing. Completely reproducable.
edgy socket
This might do the trick. https://github.com/NousResearch/hermes-agent/pull/10647 @glad echo or @sage flax please review and merge if good.
sage flax
Logs not showing anything related. No errors, nothing. Completely reproducable.
Merged to main 🙂