Unattended agent runs

Run recurring work with explicit authority, durable state, bounded resources, and recovery that does not repeat external actions.

When to use

• A scheduled process checks an inbox, calendar, task queue, or issue pool.
• A long-running agent receives recurring work from a local producer.
• A run must recover safely after a restart or context loss.
• The operator needs proof that messages, files, or other external actions landed.

When not to use

• A person is actively supervising one short task.
• The work has no stable authorization or escalation policy.
• The requested action needs a person at the moment it occurs.
• A one-off batch can use a normal interactive session.