Backend ABC and stays backend-agnostic; a concrete backend (celery, rq, arq) implements it and registers through the handle.
Implement the contract
SubclassBackend and implement launch — start the worker runtime for the backend and keep it running. That is the whole abstract surface. This example has no separate runtime, so its launch returns immediately:
examples/backend/inline_backend.py
Register through the handle
Decorate the class with@tai42_app.backends.register_backend, as the example does. Usable bare or called.
Load it
The host selects the backend by naming its module underbackend_module, then starts its worker runtime with tai backend.
manifest.yml
TAI_BUS_REDIS_URL, or tai backend refuses to start.
Keep any broker driver behind an optional extra; document broker URLs and worker settings in your repository’s README.
Shipped implementations
Shipped backends appear in the ecosystem catalog, each linking to its own repository.See also
- Backends — the execution model.
- Schedule a tool — scheduled runs execute on the backend.
- Python SDK reference — the
Backendcontract surface.

