The logs of the Hermes Agent are mainly for ~/.hermes/logs/ and hermes logs. After v0.8.0 centralizes logs, common troubleshooting does not need to be flipped everywhere: generally look at the errors.log first, then look at the agent.log, and then look at the gateway-related logs if it is a messaging platform problem.
How to use the three log entries
| entrance | What is suitable for troubleshooting |
|---|---|
hermes logs | Quick tail, filter the recent running status |
errors.log | Startup failure, tool error, and configuration error |
agent.log | Model calls, tool executions, and session flows |
| gateway log | Telegram, Discord, Slack, Webhook sending and receiving issues |
Recommended troubleshooting order
- Reproduce the problem first, don't change the configuration based on impressions alone.
- Run
hermes logsto see recent errors. - If it fails at the start-up stage, run
hermes config checkfirst. - If the gateway does not reply to the message, see the platform token, allowlist, channel permissions, and gateway logs.
- If the model is slow or failing, see provider, model name, 429/402/authentication error.
Don't post any logs
While Hermes Agent will do secrets redaction, you should still check it before sending it to the community or colleagues, especially the URL query, headers, platform token, private file path, and user ID. If you can post the error type and the last few dozen lines, don't post the entire log.
A tip: save the error log fragment before changing the configuration, and then compare whether the same task is shorter and whether there are fewer similar errors. This makes it easier to find the real reason than "reinstall".
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
