r5d-worker

Bun CLI for the durable host executor and independently supervised adapter manager used by the runtime. Provision private environment-scoped configuration with r5dinfra.

r5d-worker executor /absolute/private/executor-config.json
r5d-worker manager /absolute/private/manager-config.json

The executor retains processes and durable receipts independently of application releases. The manager authenticates the approved workspace keeper and retains old adapters until their delivery receipts are settled. Configuration and host roots belong exclusively to one installation. Never share an executor's state directory, credentials or workspace root between environments.

The published worker contains its own exact-version r5dctl build. A worker resolves that internal CLI before the host PATH, verifies its package boundary, and exposes it to agent shells through a private worker-owned wrapper. Each worker remains bound to one server origin and installation, so stage, production, and review workers cannot accidentally select another environment's global CLI or credentials.

Personal workers (r5d-worker start --label my-worker) update themselves by default. Authenticated polls check the environment's exact release once a minute; npm installs verified packages into private version directories. Once an update is ready the worker holds new shells, terminals and workspace operations back (for at most a minute), finishes the workspace operations already running, and restarts into the update. Running shells and terminals belong to a separate keeper process and move to the updated worker; read-only traffic never delays the switch. The new worker supplies its matching internal r5dctl. Global packages stay intact. --no-auto-update saves an opt-out for the selected origin, label and state root, and --auto-update saves an opt-in that replaces it. A worker run from source keeps updates off unless started with --auto-update. Executor/manager service commands do not use this updater. See client updates.

r5d-worker start --remote --label <label> [--cwd <dir>] connects a machine as a remote (#356): the same keeper, registration, updates and terminal stream, but no workspace. Agents run commands and file tools there with their worker parameter while the conversation stays on its worker; the Shell page opens terminals there. See remotes.