Skip to main content
A backend is where work runs when it does not run inline: queued tool calls, schedules, and agent turns. Three shipped backends implement the same contract — pick one, name its package in the manifest, and run a worker process against it.
Every registered backend needs the worker bus: TAI_BUS_REDIS_URL must be set, or boot is refused. Stacks sharing one Redis must also diverge on TAI_BUS_NAMESPACE (default tai).

​
Install and run one

Each backend’s package, its backend_module manifest key, its <PREFIX>_* settings, the worker/beat/dashboard commands it accepts, and its contract-coverage quirks live on the plugin page:

backend-arq

ARQ_* settings and the single worker process.

backend-celery

CELERY_* settings, beat and flower, and the prefork concurrency caveat.

backend-rq

RQ_* settings, worker, beat, and the dashboard.

​
See also