Administer Maia

Authorize automation

Create scheduled work and require human authorization for sensitive runs and commands.

Maia can run scheduled prompts and scripts. Authorization checkpoints prevent a recurring schedule from becoming an automatic grant to perform sensitive work.

Create a scheduled job

Use the dashboard Cron page or the CLI:

maia cron add

A job can use a duration such as 2h, a phrase such as every monday 9am, a five-field cron expression, or a one-time ISO timestamp.

Schedule examples

30m
every monday 9am
0 9 * * 1
2026-08-01T13:00:00Z

Require authorization

Create or edit the job.
Enable Require authorization checkpoint.
Select approver roles, specific approver users, or both.
Save the job and run a manual test.
Approve and deny separate test runs to verify both paths.

When a due job requires authorization, it enters awaiting_authorization. A recurring job requires a fresh decision for each protected run.

Manage jobs

maia cron list
maia cron run <job_id>
maia cron pause <job_id>
maia cron resume <job_id>
maia cron remove <job_id>

Approve sensitive commands

Terminal access and command approval are related but different. A role can be permitted to use terminal tools while flagged commands still require an authorized reviewer.

governance:
  terminal:
    allowed_roles: [operator]
    approver_roles: [manager, admin]

approvals:
  mode: smart

Do not approve from the prompt alone.

Review the exact command, working directory, affected files or services, requesting identity, and expected result.

Understand creator context

Agent-backed cron jobs restore their creator identity. That means personal memory, skills, teams, and governance rules are evaluated for the creator rather than for an anonymous scheduler.