Summary

qmd's onBoot setting only works for the "main" agent. It doesn't start the others.

Steps to reproduce

1. configure qmd, with onBoot: true
2. start the gateway
3. observe that only the "main" agent gets indexed

Expected behavior

02:10:26 [gateway] qmd memory startup initialization armed for agent "main"
02:10:27 [gateway] qmd memory startup initialization armed for agent "third"

Actual behavior

02:10:26 [gateway] qmd memory startup initialization armed for agent "main"

OpenClaw version

2026.2.14

Operating system

Linux DietClaw 6.12.63+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.63-1 (2025-12-30) x86_64 GNU/Linux

Install method

npm global

Logs, screenshots, and evidence

02:10:26 [gateway] qmd memory startup initialization armed for agent "main"

Impact and severity

Affected: agents
Severity: annoying
Frequency: always
Consequence: bad performance

Additional information

No response