Hermes tool calling can fail through Telegram or cron
A Linux Hermes setup using Qwen 3.6 as a local LLM through LM Studio showed a channel-specific problem. The was set above 64k, and the same tools, including the terminal, were enabled for both the CLI and Telegram.
In a new dashboard or CLI chat, asking Hermes to run the `date` command correctly used the terminal tool and printed the real output. Through Telegram or a cron task, the same request did not run the tool.
The reply sometimes showed code for calling the tool without actually running it, or a wrong date. The active context was under 15k, so the problem did not look like a issue, and the same prompt worked correctly with other agents.
Key points
- The setup used Linux, LM Studio, and Qwen 3.6 as a local LLM.
- Terminal tool use worked correctly in the dashboard and CLI.
- The same failed through Telegram and cron tasks.
- Failures included showing code without execution or returning a wrong date.
- Test every Hermes channel before relying on it for .