refactor(auto-reply): unify transient failure visibility

This commit is contained in:
Ayaan Zaidi
2026-06-03 13:43:14 +05:30
parent a5ef086e3c
commit 1bd1483b62
3 changed files with 35 additions and 56 deletions

View File

@@ -194,10 +194,12 @@ OpenClaw resolves that behavior by conversation type:
`message(action=send)`.
- Internal orchestration allows silence by default.
OpenClaw also uses silent replies for internal runner failures that happen
before any assistant reply in non-direct chats, so groups/channels do not see
gateway error boilerplate. Direct chats show compact failure copy by default;
raw runner details are shown only when `/verbose full` is enabled.
OpenClaw also uses silent replies for generic internal runner failures in
non-direct chats, so groups/channels do not see gateway error boilerplate.
Classified failures with user-facing recovery copy, such as missing auth,
rate-limit, or overload notices, can still be delivered. Direct chats show
compact failure copy by default; raw runner details are shown only when
`/verbose full` is enabled.
Defaults live under `agents.defaults.silentReply`; `surfaces.<id>.silentReply`
can override group/internal policy per surface.