Schedule work

You schedule work on a Cmdop machine by asking for it in plain language inside an ordinary conversation on that machine — no separate scheduler screen. The machine stores the instruction, runs it when its time arrives, and writes the result back into the same session. Most people come here to set up a recurring check.

For example:

Every weekday at 09:00, check the open release blockers and give me a short status.

In 30 minutes, check whether the deployment finished and summarize the result.

Each request arms a schedule on that machine. When it fires, the result lands back in the session history, so you can read it even if no browser was open.

To review or cancel what is armed — per machine or across the fleet, with last and next fire times — see Armed schedules.

Related

• The web console
• Skills — package a repeatable capability.

Common questions

How do I schedule work from the web console?

Ask for the schedule in an ordinary conversation on the machine that should do the work. The phrasing is the schedule; there is no separate scheduler form to wire up first.

Where do scheduled results appear?

The fired schedule returns as a fresh turn in the same session that created it, so the result is visible in that session history even if no browser was open.

How do I cancel an armed schedule?

Use the armed schedules view to review and delete schedules per machine or across the fleet, including their last and next fire times.