Skip to main content
Every unit of work in IronClaw is a job. Jobs run in parallel, each with isolated context, and each progressing through a defined state machine until they complete, fail, or get recovered.

Configuration


Job State Machine

States

Transitions

A job enters Stuck when the self-repair system detects it has been InProgress with no activity for longer than the configured timeout. The system then attempts recovery by re-entering InProgress with a fresh worker. If recovery fails repeatedly, the job transitions to Failed.

Parallel Execution

IronClaw runs multiple jobs concurrently. Each job has its own isolated context — memory, tool call history, and conversation state. When all job slots are occupied, new jobs queue as Pending until a slot opens. The scheduler dispatches queued jobs in order of creation time.
Increasing MAX_PARALLEL_JOBS increases LLM API concurrency. Set it according to your API rate limits and available system resources.

Job Tools

Four built-in tools let the agent manage jobs at runtime: