Backend plugin · listing tai42/backend-arqInstall
Permissions
Provides
arq
Backend — arq execution backend — background tool runs and schedules over Redis.
The arq backend runs queued tool calls, schedules, and agent turns over a single
Redis — no separate broker. It is the default the distribution bundle selects.
Enable it
manifest.yml
Configuration
TheARQ_ env group. ARQ_REDIS_URL and ARQ_REDIS_MAX_CONNECTIONS fall back
to the shared TAI_DEFAULT_REDIS_URL / TAI_DEFAULT_REDIS_MAX_CONNECTIONS
namespace when unset; a set ARQ_ value always wins.
Run the worker
worker is the only tai backend subcommand this backend accepts
— there is no beat or dashboard process, and anything else is refused by name.
Worker lifecycle
Everything around the arq worker is the shared backend lifecycle every backend gets, not this plugin’s own: the launch waits for the app’s boot self-resync before the worker consumes (a worker running against a half-built tool registry would fail its jobs permanently), the first SIGTERM or SIGINT asks arq for a warm drain, a repeated one escalates to a cold stop, and the drain is awaited to completion before the process tears down. arq is deliberately built with its own signal handlers disabled. The host owns the process’s signal disposition and composes every subscriber onto one handler per signal; arq’s install would replace that outright and take the server’s teardown with it, which is what makes a recycle drain cleanly instead of severing in-flight jobs.Quirks
ARQ_MANIFEST_KEY,ARQ_TASK_TIMEOUT, andARQ_TOOL_NAME_ARGmirror the host’s ownBACKEND_group. Change them in lockstep or the worker and the server stop agreeing.ARQ_MANIFEST_KEYandARQ_TOOL_NAME_ARGpin wiring built at boot, so a change to either converges through a process recycle rather than in place.ARQ_JOB_COMPLETION_WAITmust cover the longest job, and the deployment’s termination grace period must be at least as long, or a drain still severs running work. arq cancels running jobs on signal unless this is non-zero.
See also
- Backends — the contract all three shipped backends implement.
- Manage a fleet — reading the live worker census.
- Schedule a tool — putting work on a schedule.

