fix(messages): restore explicit responsePrefix default
This commit is contained in:
@@ -937,8 +937,7 @@ See [Messages](/concepts/messages) for queueing, sessions, and streaming context
|
||||
`responsePrefix` is applied to **all outbound replies** (tool summaries, block
|
||||
streaming, final replies) across providers unless already present.
|
||||
|
||||
If `messages.responsePrefix` is unset and the routed agent has `identity.name`
|
||||
set, Clawdbot defaults the prefix to `[{identity.name}]`.
|
||||
If `messages.responsePrefix` is unset, no prefix is applied by default.
|
||||
|
||||
If `messages.messagePrefix` is unset, the default stays **unchanged**:
|
||||
`"[clawdbot]"` when `whatsapp.allowFrom` is empty, otherwise `""` (no prefix).
|
||||
|
||||
@@ -59,8 +59,8 @@ When the wizard asks for your personal WhatsApp number, enter the phone you will
|
||||
}
|
||||
```
|
||||
|
||||
Tip: if you set the routed agent’s `identity.name`, you can omit
|
||||
`messages.responsePrefix` and it will default to `[{identity.name}]`.
|
||||
Tip: set `messages.responsePrefix` explicitly if you want a consistent bot prefix
|
||||
on outbound replies.
|
||||
|
||||
### Number sourcing tips
|
||||
- **Local eSIM** from your country's mobile carrier (most reliable)
|
||||
|
||||
Reference in New Issue
Block a user