chimera cron

Manage scheduled jobs (crons and event SOPs).

Subcommands

chimera cron add

Add a cron, event- or webhook-triggered job. `--verify` is what turns a scheduled job into a run the harness governs. `CronJob` has carried the field since the harness landed and nothing could write it — not this command, not the HTTP route — so for every user the gate was permanently unarmed.

Arguments

NAMEstrrequired
A human-readable name.
SCHEDULEstrrequired
Cron expression, or an event/webhook name.
ACTIONstrrequired
What to do (task description / skill).

Options

--eventboolean
Treat SCHEDULE as an event name.
--webhookboolean
Fire on POST /webhook/<SCHEDULE> (needs 'chimera serve').
--verifystrdefault: ''
Gate: shell command run in the job's folder after the dispatch (exit 0 to keep the work, non-zero to revert it). Empty = no gate, which is the previous behaviour.
--max-attemptsintdefault: 1
Attempts per dispatch. Worth raising only with --verify: without a gate nothing can tell a failed attempt from a finished one.

chimera cron disable

Disable a job without deleting it.

Arguments

JOB_IDstrrequired
The job id to disable.

Options

This command takes no options.

chimera cron doctor

Ask the schedule what it is not telling you: what never ran, and what ran and lost. Every other honesty mechanism here sits downstream of a run having happened. This is the one question about the run that did not — and about the one that happens on time, forever, and fails every time, which looks healthier than the first from any field that existed before. It is a question, not a watcher: nothing notices while this process is down, for the same reason a crashed process cannot log its own crash. What it gives you is an honest answer the moment you ask.

Options

--gracefloatdefault: 10.0
How late a job may be before it counts as missed.

chimera cron enable

Enable a job (e.g. an agent-proposed one) and schedule its next run.

Arguments

JOB_IDstrrequired
The job id to enable.

Options

This command takes no options.

chimera cron fire

Run every job registered for an event. Event jobs had no dispatcher. `cron add --event deploy` accepted the job and `cron list` showed it enabled, but nothing in the package ever called `fire_event` — so the job simply never ran, and its silence was indistinguishable from that of a job whose time had not come. The cron trigger has the daemon and the webhook trigger has the webhook server; this is the third one's. Meant to be called from wherever the event actually happens — a git hook, a deploy step, a CI job. Dispatch is the same one the daemon uses, so a fired job behaves exactly like a scheduled one: same agent, same spend caps, same receipt.

Arguments

EVENTstrrequired
The event name to fire (as given to `cron add --event`).

Options

--model, -mstr
Model for the dispatched jobs.
--max-stepsintdefault: 6
Max tool-calling steps per job.
--workspace, -wstrdefault: '.'
Workspace root for tools.

chimera cron learn

Propose crons from recurring tasks and create the ones you confirm. Each proposal is shown for explicit confirmation (the human-in-the-loop approval that keeps automation creation under control); confirmed jobs are validated and created enabled. ``--yes`` confirms all (use deliberately).

Options

--minintdefault: 3
Min repeats to propose.
--schedulestr
Override the suggested cron schedule.
--yes, -yboolean
Create every proposal without prompting.

chimera cron list

List scheduled jobs.

Options

This command takes no options.

chimera cron remove

Remove a scheduled job by id.

Arguments

JOB_IDstrrequired
The job id to remove.

Options

This command takes no options.