Skip to content
vavio

Can Hermes create, change or stop its own scheduled jobs?

Yes. When you ask in chat, Hermes can create, list, edit, pause, resume, run, cancel and remove its own scheduled jobs through its cronjob_manage tool. It cannot choose a different model, provider or reasoning effort for a job; those stay with you. Hermes does not ask for approval before changing a schedule unless you add a rule that requires it, so ask it to list the job afterwards and check the result.

This follows Hermes Agent v0.23.1, commit 3b42157, checked on 16 November 2026. We reviewed the official documentation and source; we have not run these actions on a Vavio computer. The commands below are upstream Hermes commands, not Vavio CLI commands.

What can Hermes change, and what stays your choice?

You can ask Hermes to… Stays your choice in the pinned version
Create a job from a prompt, attached skills or an existing script, optionally paused Which model, provider or endpoint a job uses
Change its schedule, prompt, name, skills, timezone, repeat count or catch-up setting The job’s reasoning effort and script interpreter
Change where results and failure notices are delivered Whether scheduled runs may manage jobs (cron.allow_agent_scheduling)
Choose which tools a job’s run may use, or the folder it runs from Whether unattended runs may run commands flagged as dangerous (approvals.cron_mode)
Turn a job into a script-only job that skips the model Tools you disable under agent.disabled_toolsets
Pause, resume, run once now, cancel the current run or remove the job

The model limit is deliberate. Hermes’s source keeps per-job model, provider and endpoint choices out of the tool so the agent cannot point unattended spend at a different model. Hermes can pin the model you already use to a job, or release a pin so the job follows your main model again, and its instructions say to do that only when you ask. Releasing a pin also clears a model and provider you set yourself. To choose a different model for one job, use the dashboard or hermes cron edit. Can a scheduled Hermes job use a cheaper model covers that choice.

Hermes can set a job’s own tool list, and that list replaces your default tool set for scheduled runs, so it can include a toolset you only turned off for scheduled runs. Scheduled runs never receive the messaging or clarifying-question tools, and toolsets you disable under agent.disabled_toolsets stay disabled for them. A job’s working folder can be any existing folder; Hermes loads that folder’s instruction files, such as AGENTS.md, for the run.

Can a scheduled job change the schedule by itself?

Not by default. A run started by the scheduler does not receive the scheduling tool, so a job cannot create, edit or remove jobs. Hermes’s source describes this as loop prevention rather than a security boundary. You can opt in through your profile’s config.yaml:

cron:
  allow_agent_scheduling: true   # default: false

With it on, a scheduled run can manage the job list just as a chat can. The upstream guide gives three uses: a job that schedules a one-off follow-up, a job that tunes its own frequency, and a “librarian” job that reviews the whole list. Jobs created this way go into the same list as the jobs you created, with no special owner, so you can edit or remove them in the usual way.

Two documented details matter if you turn it on. A job created from inside a scheduled run that asks to deliver to “here” is pointed at the creating job’s own destination when it is created, so it never delivers to a session that no longer exists. A recurring job can also remove itself and still deliver its final answer, which suits “watch for this, tell me once, then stop”.

Upstream advises prompts that list jobs first and update one by ID rather than creating a new job on every run. Otherwise a recurring job can keep adding near-duplicates.

Does Hermes ask before it changes a job?

Not by default. In the pinned source, creating, editing, pausing and removing a job are not on Hermes’s built-in approval list. The tool does apply some checks of its own:

  • Prompt checks. A new or edited prompt is refused if it contains hidden Unicode characters, instruction-override phrases, or commands shaped like reading credential files, changing SSH or sudo access, deleting from the root folder, or sending a secret variable to a web address with curl or wget. These are fixed text patterns, so a reworded instruction can pass.
  • Scripts. A job can only use a script that already exists in the profile’s scripts folder. Absolute paths and paths that escape that folder are refused. Hermes can still write a new script there from chat first, and a job’s script runs as written, without the dangerous-command check below.
  • Names. You can refer to a job by name. If two jobs share the name, Hermes refuses and lists their IDs rather than guessing.
  • Unattended runs. By default, a scheduled run cannot run a shell command that Hermes flags as dangerous unless you have permanently approved it, because no one is present to approve it. Which actions Hermes asks you to approve explains that setting and its exceptions.

If you want a confirmation step for schedule changes, Hermes’s plugin and shell hooks can return approve for a named tool before it runs. That sends cronjob_manage calls to the same approval prompt used for dangerous commands; a denial or timeout blocks the call. Turning approvals off, or answering “always”, lets matching calls through without a prompt. Inside a scheduled run, that request follows your approvals.cron_mode setting, which denies by default. We have not tested such a hook.

For a new job you are unsure about, ask Hermes to create it paused with a reason. The job is stored without being scheduled, so you can read it before anything runs. Pausing prevents automatic runs, not a run or resume that you or Hermes asks for.

How do I check what Hermes changed?

Each create or update returns the job’s resulting settings, so Hermes can show you what it stored. To check afterwards, ask for the list or, if you can reach the Hermes command line, run:

hermes cron list --all
hermes cron runs <job_id> --limit 20

Replace <job_id> with the job’s ID. Hermes’s own list shows each job’s prompt preview, model pin, schedule, delivery target, state, next run and last status. hermes cron list --all shows the schedule, delivery, state, next run and last run, but not the prompt or model. Both show current settings, not a history of edits. If you need to know what a job looked like before Hermes changed it, ask Hermes to list the job before the change and keep that output. Run history records attempts and outcomes; it does not record configuration edits.

A useful request is:

List my scheduled jobs. Change “Morning research” to run at 7am on weekdays and keep everything else the same. Do not create a new job. Then list that job again and show me its schedule, delivery target and next run.

Should I let Hermes remove jobs?

Removal is the one action that loses information. Removing a job deletes it, its saved output folder and its notepad, and stops any run that is in progress. Pausing keeps all of that while stopping future runs. If you are not sure, ask Hermes to pause the job instead. How to stop a running Hermes job without deleting its schedule compares pause, cancel and remove.

None of these actions undoes what a job has already done. A message that has been sent or a record that has been changed stays as it is after the job is paused or removed.

Vavio supplies a managed remote Hermes computer for $14.99 per month, with model usage billed separately. It keeps the Hermes runtime off your laptop; checking what a job will do before it runs is still your call. See the current hosting offer, or use the same controls on a Hermes server you maintain yourself.

Sources

Written by Vavio with AI assistance and checked against pinned official Hermes v0.23.1 documentation and source. This is a source review, not a live scheduling trial.

More from the Vavio blog: Hermes Agent guides