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
|
|
@ -269,6 +269,7 @@ zeroclaw integrations info Telegram
|
|||
# Manage background service
|
||||
zeroclaw service install
|
||||
zeroclaw service status
|
||||
zeroclaw service restart
|
||||
|
||||
# Migrate memory from OpenClaw (safe preview first)
|
||||
zeroclaw migrate openclaw --dry-run
|
||||
|
|
@ -518,6 +519,10 @@ WhatsApp uses Meta's Cloud API with webhooks (push-based, not polling):
|
|||
|
||||
Config: `~/.zeroclaw/config.toml` (created by `onboard`)
|
||||
|
||||
When `zeroclaw channel start` is already running, changes to `default_provider`,
|
||||
`default_model`, `default_temperature`, `api_key`, `api_url`, and `reliability.*`
|
||||
are hot-applied on the next inbound channel message.
|
||||
|
||||
```toml
|
||||
api_key = "sk-..."
|
||||
default_provider = "openrouter"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue