docs: document autonomy notification target derivation from channel allow_from

This commit is contained in:
DBT
2026-03-01 03:45:59 +00:00
parent 189516d817
commit 56875f56d0
2 changed files with 2 additions and 0 deletions

View File

@@ -66,6 +66,7 @@ Autonomy now supports lock scheduling via `resource_keys`. You can explicitly de
- Example: `[keys: repo:clawgo, file:pkg/agent/loop.go, branch:main] fix dialog flow`
- Without explicit keys, the engine derives keys from task text heuristically.
- Conflicting tasks enter `resource_lock` waiting, retry lock acquisition after 30s, and use fairness weighting (longer wait => higher scheduling priority).
- Autonomy completion/blocked notifications no longer use `autonomy.notify_channel` / `autonomy.notify_chat_id`; target is derived from enabled channel `allow_from` (Telegram first).
## 🏁 Quick Start