Hermes Agent is a desktop AI agent tool whose test coverage to date has focused on two setup-dependent features: scheduled Cron jobs and email integration via IMAP and SMTP. Both accounts come from hands-on testing that found features only work as expected once specific background or header conditions are met.
Recent coverage of Hermes Agent has come from hands-on testing of two features, and both tests found that the tool depends on setup steps outside the feature itself. The Cron feature schedules AI agent tasks at set times or intervals. A five-minute output job ran on schedule, but a second job did not fire while the desktop app was closed, and only ran when the app was relaunched. Installing the Gateway background process with the command 'hermes gateway install' in Windows PowerShell fixed this, letting jobs run while the app is closed as long as the PC is on and logged in.
The email gateway test followed a similar pattern. Connecting Hermes Agent to email over IMAP and SMTP did not work after adding an allowed sender; replies still did not arrive. The logs showed the error 'no Authentication-Results header.' The email account used, Sakura's Mailbox, added ARC-Authentication-Results instead, which Hermes Agent does not read for sender authentication. So the email integration depends on a specific authentication header that some providers do not supply in that form.
Taken together, the two accounts describe the same state of affairs: Hermes Agent's unattended and external-channel features work, but only after the right supporting process or header is in place. The Cron test settled that the Gateway process is what makes scheduled jobs run without the app open. The email test settled that sender authentication hinges on the Authentication-Results header specifically, not the ARC variant.
Synthesized by Yomimono from the cited Yomimono stories below, each itself
sourced, then editorially reviewed. Every
fact links the story it came from.
Facts
- Noted
- Hermes Agent email integration requires Authentication-Results header · 2026-09-04
- Noted
- Hermes Agent's Cron feature schedules AI agent tasks at set times or intervals. · 2026-09-02
- Noted
- A five-minute output job ran on schedule. · 2026-09-02
- Noted
- A second job did not fire while the desktop app was closed and only ran when the app was relaunched. · 2026-09-02
- Noted
- Installing the Gateway background process via 'hermes gateway install' in Windows PowerShell fixed this. · 2026-09-02
- Noted
- Jobs run while the app is closed as long as the PC is on and logged in. · 2026-09-02
- Noted
- The Cron feature only becomes true unattended automation when paired with the Gateway background process. · 2026-09-02
- Noted
- The Gateway background process is required for jobs to fire while the desktop app is closed. · 2026-09-02
Structured graph also available as JSON at /public/entities/hermes-agent.
CC BY 4.0.
6d ago
GIGAZINE tested connecting Hermes Agent to email via IMAP and SMTP. After adding an allowed sender, replies still did not arrive. Logs showed the error 'no Authentication-Results header.' The email account used, Sakura's Mailbox, added ARC-Authentication-Results instead, which Hermes Agent does not read for sender authentication.
Sep 2
GIGAZINE tested Hermes Agent's Cron feature, which schedules AI agent tasks at set times or intervals. A five-minute output job ran on schedule, but a second job did not fire while the desktop app was closed and only ran when the app was relaunched. Installing the Gateway background process via 'hermes gateway install' in Windows PowerShell fixed this, letting jobs run while the app is closed as long as the PC is on and logged in.