mirror of https://github.com/openclaw/openclaw.git
a42e3cb78a
* feat(heartbeat): add accountId config option for multi-agent routing Add optional accountId field to heartbeat configuration, allowing multi-agent setups to explicitly specify which Telegram account should be used for heartbeat delivery. Previously, heartbeat delivery would use the accountId from the session's deliveryContext. When a session had no prior conversation history, heartbeats would default to the first/primary account instead of the agent's intended bot. Changes: - Add accountId to HeartbeatSchema (zod-schema.agent-runtime.ts) - Use heartbeat.accountId with fallback to session accountId (targets.ts) Backward compatible: if accountId is not specified, behavior is unchanged. Closes #8695 * fix: improve heartbeat accountId routing (#8702) (thanks @lsh411) * fix: harden heartbeat accountId routing (#8702) (thanks @lsh411) * fix: expose heartbeat accountId in status (#8702) (thanks @lsh411) * chore: format status + heartbeat tests (#8702) (thanks @lsh411) --------- Co-authored-by: m1 16 512 <m116512@m1ui-MacBookAir-2.local> Co-authored-by: Gustavo Madeira Santana <gumadeiras@gmail.com> |
||
|---|---|---|
| .. | ||
| security | ||
| authentication.md | ||
| background-process.md | ||
| bonjour.md | ||
| bridge-protocol.md | ||
| cli-backends.md | ||
| configuration-examples.md | ||
| configuration.md | ||
| discovery.md | ||
| doctor.md | ||
| gateway-lock.md | ||
| health.md | ||
| heartbeat.md | ||
| index.md | ||
| local-models.md | ||
| logging.md | ||
| multiple-gateways.md | ||
| network-model.md | ||
| openai-http-api.md | ||
| openresponses-http-api.md | ||
| pairing.md | ||
| protocol.md | ||
| remote-gateway-readme.md | ||
| remote.md | ||
| sandbox-vs-tool-policy-vs-elevated.md | ||
| sandboxing.md | ||
| tailscale.md | ||
| tools-invoke-http-api.md | ||
| troubleshooting.md | ||