1.9 KiB
1.9 KiB
summary, read_when
| summary | read_when | |
|---|---|---|
| When Clawdbot shows typing indicators and how to tune them |
|
Typing indicators
Typing indicators are sent to the chat provider while a run is active. Use
agent.typingMode to control when typing starts and typingIntervalSeconds
to control how often it refreshes.
Defaults
When agent.typingMode is unset, Clawdbot 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 is disabled.
Modes
Set agent.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).
Order of “how early it fires”:
never → message → thinking → instant
Configuration
{
agent: {
typingMode: "thinking",
typingIntervalSeconds: 6
}
}
You can override mode or cadence per session:
{
session: {
typingMode: "message",
typingIntervalSeconds: 4
}
}
Notes
messagemode won’t show typing for silent-only replies (e.g. theNO_REPLYtoken used to suppress output).thinkingonly fires if the run streams reasoning (reasoningLevel: "stream"). If the model doesn’t emit reasoning deltas, typing won’t start.- Heartbeats never show typing, regardless of mode.
typingIntervalSecondscontrols the refresh cadence, not the start time. The default is 6 seconds.