Typing indicators are sent to the chat channel while a run is active. UseDocumentation Index
Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt
Use this file to discover all available pages before exploring further.
agents.defaults.typingMode to control when typing starts and typingIntervalSeconds
to control how often it refreshes.
Defaults
Whenagents.defaults.typingMode is unset, OpenClaw keeps the legacy behavior:
- Direct chats: typing starts immediately once the model loop begins.
- Group chats with a mention: typing starts immediately.
- Group chats without a mention: typing starts only when message text begins streaming.
- Heartbeat runs: typing starts when the heartbeat run begins if the resolved heartbeat target is a typing-capable chat and typing is not disabled.
Modes
Setagents.defaults.typingMode to one of:
never— no typing indicator, ever.instant— start typing as soon as the model loop begins, even if the run later returns only the silent reply token.thinking— start typing on the first reasoning delta (requiresreasoningLevel: "stream"for the run).message— start typing on the first non-silent text delta (ignores theNO_REPLYsilent token).
never → message → thinking → instant
Configuration
Notes
messagemode won’t show typing for silent-only replies when the whole payload is the exact silent token (for exampleNO_REPLY/no_reply, matched case-insensitively).thinkingonly fires if the run streams reasoning (reasoningLevel: "stream"). If the model doesn’t emit reasoning deltas, typing won’t start.- Heartbeat typing is a liveness signal for the resolved delivery target. It
starts at heartbeat run start instead of following
messageorthinkingstream timing. SettypingMode: "never"to disable it. - Heartbeats do not show typing when
target: "none", when the target cannot be resolved, when chat delivery is disabled for the heartbeat, or when the channel does not support typing. typingIntervalSecondscontrols the refresh cadence, not the start time. The default is 6 seconds.