Create a cron job by asking AI
Omniscio's built-in cron scheduler can be driven by an outside AI: describe the schedule in plain English and the AI creates the job, which then waits for your approval before it ever runs. Covers enabling CLI Control, phrasing one-off and limited jobs, the approval step, and how to revoke the AI's access to your machine.
On this page
What it is
Omniscio has a built-in cron scheduler — jobs that run on your machine at a fixed schedule (every hour, daily at 9am, a custom cron expression, etc.). You can create one manually in the Cron Jobs UI, or you can just tell an external AI — Claude Code in any project on your machine — "schedule X every day at 9am" and it will create the job for you. The AI uses the omniscio-control skill bundle (cron surface), which reads an auto-delivered token from ~/.amc/cli-token and POSTs to Omniscio's local control server at 127.0.0.1:19519. You still have to approve the first run from Omniscio's inbox, so a rogue or buggy AI cannot silently run code on your machine.
Where to find it
Cron jobs themselves live in the Cron Jobs surface — the middle pane on desktop — where a job appears with an approval badge until you arm it, and where you can also create one by hand. The switch that lets an outside AI create jobs for you is in Settings → CLI Control, and that page is also where you regenerate or revoke the token afterwards.
How it behaves
How to use it
Enable CLI Control once. Open Omniscio → Settings → CLI Control and flip it on. Omniscio starts its local control server and writes your auth token to
~/.amc/cli-token(on Windows,%USERPROFILE%\.amc\cli-token). The file is permission-hardened (0o600on Unix, an ACL grant to your user on Windows) and deleted when you disable CLI Control or quit Omniscio.Ask an AI in plain English. In any Claude Code session (any project on your machine) say something like "schedule a cron to run
python backup.pyevery day at 9am" or "set up a recurring job to sync email hourly". Theomniscio-controlskill bundle (cron surface) auto-activates on trigger phrases like cron job, every day at…, every N hours, schedule X nightly, recurring job.Pick a mode by how you phrase it. Say "every day at 9am" for a recurring job, "once tomorrow at 9am" for a one-off job that fires once and stops, or "run X three times daily" for a limited job that stops after N runs. The AI picks the right mode automatically — you don't need to say "one-off" or "limited" explicitly.
Answer the skill's questions. The skill will batch ~5 questions in one round: job name, what it runs (shell command or an existing Omniscio recipe ID), when (preset like "daily at 9am" or a raw 5-field cron expression), optional timeout (default 300 s). It also writes a short plain-English description of what the job does — you don't have to supply one; the AI composes it so the approval card reads clearly. It translates your schedule to cron syntax using its built-in cheat sheet.
Approve the first run. After the skill POSTs the job, open Omniscio → Cron Jobs (middle pane on desktop). Your new job appears with an orange Awaiting approval badge. The approval card shows the job in plain English — a readable name (a slug like
sync-inbox-hourlyis shown as "Sync Inbox Hourly", with the raw slug on hover), the AI's description of what it does, and a humanized schedule — so you can tell what you're approving at a glance. Click Approve to arm it. The create answer also hands the agent anapprovalUrl(omniscio://cron/job/<id>), and the job raises ONE persistent inbox card in the Approvals area — deduped per job, so creating and later editing the same job never stacks a second card, and approving or rejecting withdraws it. All AI-created jobs require approval before their first run — the server enforces this, so even a malicious AI cannot bypass it.Regenerate or revoke the token if needed. Settings → CLI Control → Regenerate token rewrites
~/.amc/cli-tokenimmediately; the next AI invocation picks up the new value with no restart. Disabling CLI Control entirely deletes the file and blocks further AI access.
Rate limit: AI-created mutations (create/update/delete/toggle) are capped at 10/min. The skill surfaces this if you hit it.
Related
The skill bundle this leans on is one of several installed into Claude Code, so how skills work is worth reading if you have not met them before. The approval step above is an instance of the same waiting-for-you machinery that runs through the app, which is described on the approvals hub page. If a scheduled job is what you want rather than a recurring shell command, the cron session jobs page covers starting whole agent sessions on a schedule instead.
- use-skills.md — how skills work in general (install, edit, trusted-source gate)
- session-stuck-in-needs-you.md
Last verified 2026-10-26