CLI
tai backend
Run a tai execution-backend runtime (worker / beat / dashboard).
Run a tai execution-backend runtime (worker / beat / dashboard).
A backend runtime always registers a task backend, so it requires the worker
bus — set TAI_BUS_REDIS_URL. The backend-runtime and server processes must
converge on config reloads, so a busless backend is refused at boot (and again
on any reload that would leave a backend without the bus). A non-file
TAI_CONFIG_MODE is likewise refused without the bus.
It also requires the shared hooks registry — set HOOKS_REDIS_URL (or
TAI_DEFAULT_REDIS_URL). The events this process raises are matched against
its own registry, and an in-memory one holds none of the hooks registered
through the server, so a backend over it is refused at boot and on reload.
A runtime whose engine must patch the interpreter before anything else is
imported (a green worker pool) starts once, reads its configuration, and then
restarts itself in place with that patch applied first: same process id, same
arguments, one “restarting with process prelude” log line.

