fix(channel): hot-apply runtime config updates for running channel service
This commit is contained in:
parent
95ec5922d1
commit
740eb17d76
7 changed files with 410 additions and 22 deletions
|
|
@ -349,6 +349,7 @@ Notes:
|
|||
- When a timeout occurs, users receive: `⚠️ Request timed out while waiting for the model. Please try again.`
|
||||
- Telegram-only interruption behavior is controlled with `channels_config.telegram.interrupt_on_new_message` (default `false`).
|
||||
When enabled, a newer message from the same sender in the same chat cancels the in-flight request and preserves interrupted user context.
|
||||
- While `zeroclaw channel start` is running, updates to `default_provider`, `default_model`, `default_temperature`, `api_key`, `api_url`, and `reliability.*` are hot-applied from `config.toml` on the next inbound message.
|
||||
|
||||
See detailed channel matrix and allowlist behavior in [channels-reference.md](channels-reference.md).
|
||||
|
||||
|
|
@ -425,6 +426,7 @@ After editing config:
|
|||
zeroclaw status
|
||||
zeroclaw doctor
|
||||
zeroclaw channel doctor
|
||||
zeroclaw service restart
|
||||
```
|
||||
|
||||
## Related Docs
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue