Quick start
Task lifecycle
Execution contracts
Every task has a contract that defines what kind of work it represents:- runner.chat.v1
- job.dispatch.v1
- Custom contract
Standard agent chat. Runs an agent with a user message.
Worker setup
1
Create a worker
2
Register custom contract handlers
3
Start the worker
Dead-letter handling
When a task exhausts all retries, it moves to the dead-letter queue (DLQ):Error classification
The queue uses error classification to decide whether to retry:Queue backends
- In-memory (default)
- Redis
State lives in process memory. No setup required.Use for: Development, testing, prototyping.
Connection pooling
For high-throughput production workloads, useRedisConnectionPool to manage connections efficiently:
- Configurable max connections (default: 50)
- Idle connection management
- Automatic health checks
- Singleton access via
get_redis_pool()
Next steps
MCP Server
Expose tools via the Model Context Protocol.
Observability
Monitor queue performance and worker health.