Hermes Agent Cron Jobs Run Without the App After Gateway Setup
The Cron feature only becomes true unattended automation when paired with the Gateway background process, which the article shows is required for jobs to fire while the desktop app is closed.
Reporting from 1 source: GIGAZINE.
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.
The first test set a job to print 'Cron automatic execution succeeded' five minutes out, and the Scheduled jobs panel showed it ran at 17:12, about five minutes after setup. The same relative-time method can schedule a daily 9 a.m. action or a subscription renewal reminder.
The second test exposed the limit: with the desktop app closed, the job did not fire on schedule and only ran when the app was relaunched. Running 'hermes gateway install' in Windows PowerShell starts a background Gateway process that executes Cron jobs and registers a login-time autostart task in Windows Task Scheduler. A third job set for 18:31 ran on time while the app was closed, as long as the PC stays on and logged in.
Results still need manual checking, so the author plans to test sending them to Telegram, Discord, or Slack next.
Synthesized by Yomimono from the 1 cited source below, including Japanese-language reporting where cited, then editorially reviewed before publishing.