# witcheer's Wingtips #55: chaining cron jobs

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/55  
Published: 2026-08-26  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/55-chaining-cron-jobs/) · [On X](https://x.com/witcheer/status/2092527968140632114) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/55-chaining-cron-jobs.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Cron](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron)


Hermes Wingtips #55: chaining cron jobs

every cron job wakes up in a fresh session. a two-step pipeline, collect then summarize, can't see what step one produced.

`context_from` wires the connection. when you create the second job, point it at the first job's id, and the first job's latest output is prepended to the second job's prompt at fire time.

a job can also point at itself. `continuity` injects the job's own previous output. 

you set all of this by asking your Hermes Agent in plain language, it manages its own cron table.