Hermes Agent can no longer create new cron in cron tasks, not because of lack of permissions, but because the official has actively banned this type of recursive scheduling. The warning in the cron documentation states that cron-run sessions cannot recursively create more cron jobs, which is to prevent the task from spawning itself and dragging the scheduler into a runaway loop.
Why are officials so conservative
Because once a scheduled task can continue to create a scheduled task in operation, it is easy to have three problems: repeated scheduling, infinite expansion, and forgetting to recycle. Especially if you ask the agent to automatically add a new plan based on the results, a prompt deviation may generate a bunch of duplicate jobs within a few minutes.
Correct alternative
- Start by creating a fixed cron and let it conditionally decide "what to do" rather than "who to build".
- If you really want to orchestrate dynamically, use the main session or external scripts to manage jobs uniformly.
- Write changes to a configuration file, task list, or directory state, and let the existing cron read it, instead of putting a cron in it.
So there is no "fix order" in this question. It is the safety boundary of the product. If you want to do complex automation, you can let Hermes Agent read the state, modify files, and send notifications, but don't expect it to expand the cron to another layer in the cron. This design, while conservative, avoids the most difficult runaway scheduling.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
