Worker configuration
A worker is the machine that runs agent jobs and exposes a worker-gate API to the control plane. In local development, the control and worker roles can point at the same127.0.0.1:8787 app.
For current runtime topology and worker-gate boundaries, see
current runtime snapshot.
Connection fields
worker_wake_gate_url— base URL for the worker-gate API. The field name remains for compatibility.worker_wake_gate_bearer_token— bearer token the control plane uses when calling the worker.worker_targets— named worker endpoints with per-target URLs, tokens, roles, and optional memory floors.workload_machine_targets— maps workload classes such ascpu_onlyandgpu_requiredto aworker_targetskey.
worker_wake_gate_url and completion_callback_url to the local service. For production with multiple workers, configure worker_targets and route dispatches through workload_machine_targets or explicit machine_target in preflight requests.
Evidence sync fields
paper_evidence_sync_enabledpaper_evidence_sync_ssh_hostpaper_evidence_sync_remote_rootpaper_evidence_sync_timeout_sec
Stale-process reaper fields
stale_project_process_reaper_enabledstale_project_process_grace_secstale_project_process_term_grace_secstale_project_process_command_markers
llama-cli, llama-server, vllm, and sglang. Keep markers specific to avoid terminating unrelated processes.