Skip to content

AI Compass / Knowledge cards

Long-running jobs that wake the model only on change

wake gate

Checked Automation Costs

A long-running job runs on a schedule, for example every 15 minutes. On Linux, cron, the built-in scheduler, does this. If the job calls a language model every time, it costs tokens even when nothing has happened. A wake gate puts a simple check script in front. It decides by itself whether anything has changed and wakes the agent only then. AI LABS shows this with the Hermes Agent, but the pattern does not need Hermes.

What it is for

You pay for tokens only when something really happens.

Steps

  1. Choose a check task that repeats regularly, for example cost spikes or new reviews.
  2. Write a check script that reads the state and decides by itself: change yes or no. In Hermes, the script reports “no” with the last output line {"wakeAgent": false} (according to the Hermes docs, not in the video).
  3. On “no”, nothing happens. On “yes”, the agent receives the context and reports or acts.
  4. For pure monitoring, for example of certificates or payment status, use no model at all.
  5. Send the alert to a channel you see on the go. If needed, you bring the agent in with the existing context.
  6. Have actions such as replies or payments carried out only after your approval. In the video they run without approval; only posts for social networks land in a review folder first. I recommend the approval requirement.

Limits

Sources

Status

Checked 11 October 2026 · Maturity new (pattern can be rebuilt with Linux’s built-in tools, not tested by me)

Want to try this with your team? That’s what the AI Lab is for. See the AI Lab