Autorun

Autorun starts a new task automatically at a specified time, interval, or cron schedule. It does not coordinate several agents inside one run. It is an independent way to start the same kind of work when it is needed.

Requirements

Autorun requires an AGI Labo membership. Cockpit verifies membership not only at the Desktop entry point, but also in the PWA, cockpit autorun, the local API, and each scheduled execution. Requests from guests and inactive members return an explicit error. Cockpit also rejects an operation safely when a network or API failure prevents verification, but it does not cache that failure and block a member after service recovers. Existing members can use the CLI while signed in to AGI Labo in Desktop.

Schedules run inside the AGI Cockpit app process. They do not fire while Cockpit is closed, and the operating-system scheduler does not launch Cockpit for them.

Schedule types

In the cron weekday field, 0 means Sunday. For example, 0 9 * * 1-5 runs at 9:00 a.m. on weekdays.

Create an Autorun task

1. Open Autorun Tasks at the top of Desktop.
2. Select New Autorun.
3. Enter a name and the instruction to send when the task starts.
4. Choose the working directory. When running as the Master Agent, Cockpit uses the Master's working location.
5. Select an agent and, when shown, review its UI mode, launch command, and Claude or Codex account.
6. Choose Once, Interval, or Cron and configure the timing.
7. Save the Autorun and confirm that the list shows its next run time.

The approval mode and Native UI model settings used for the new task inherit the current defaults when the Autorun is created. The Autorun dialog does not have a separate model picker.

Review a run

When Autorun fires, it creates a new task in the same form as any regular task. Select it from the task list, then use task details to review its conversation, confirmation requests, errors, and results. The new task keeps a reference to the Autorun ID that created it.

The Autorun manager supports:

• enable and disable
• edit
• delete
• Run Now
• previous and next run times

Cockpit does not start another scheduled run while the previous execution turn from the same Autorun is still processing. Visual Runtime, shown as Native UI in the app, releases the lock when the turn completes, the runtime settles it, or a runtime error occurs. Terminal UI and the Terminal agent release it when the launched process exits or is cleaned up. The lock does not wait for a person to mark the Cockpit task Completed. Startup failures and cleanup paths also release it, and a 24-hour expiry is the final safeguard against an abandoned lock.

Working directory and failures

The Desktop form requires a directory unless the Autorun runs as the Master Agent. If the CLI omits the directory, Cockpit creates an agi-cockpit directory inside the operating-system temporary folder.

If the agent fails to start, the task remains in the task list with an Error state. A one-time Autorun still becomes disabled; an interval or cron Autorun remains enabled and calculates its next run. Open the created task details to inspect the cause.

If Cockpit confirms that the account is a guest or has an inactive membership when a run is due, a one-time Autorun does not start and becomes disabled. An interval or cron Autorun remains enabled and checks again at its next scheduled time. If a temporary network or API failure prevents verification, Cockpit does not start the run and checks again one minute later. It keeps a one-time Autorun enabled and persists the retry time, so a temporary outage does not consume its only run.

Create from the CLI

cockpit autorun create \
  --name "Weekday progress review" \
  --instruction "Review the unfinished work in this project and summarize it in priority order." \
  --directory /path/to/project \
  --type cron \
  --expression "0 9 * * 1-5"

cockpit autorun list
cockpit autorun run <id>
cockpit autorun toggle <id>

Related pages

• Task list and task details
• Ask