Overview

Every Allternit agent follows a defined lifecycle — from creation through execution to disposal. Understanding this lifecycle helps you build reliable, long-running agents.

States

Creating an agent

Running an agent

Suspending and resuming

When an agent requires human approval (e.g., a destructive action), it enters the suspended state. Resume with an approval decision:

Terminating an agent

Or let the agent complete naturally — the runtime cleans up resources after the final event.

Error handling

Agent errors are surfaced as events:

Best practices

  • Reuse agents for multiple runs rather than creating a new agent per request.
  • Set timeouts on long-running tasks to prevent runaway agents.
  • Monitor usage via the audit log to track token consumption and cost.
  • Handle suspension in production — agents waiting for approval will block indefinitely if never resumed.