vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 10:20:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: stop channel runtime before WhatsApp removal

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-01 22:36:58 +01:00
parent 4373103c22
commit fe8966b4ea
15 changed files with 344 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/channels/whatsapp.md
View File

@@ -492,6 +492,8 @@ Behavior notes:
<Accordion title="Logout behavior">
`openclaw channels logout --channel whatsapp [--account <id>]` clears WhatsApp auth state for that account.
When a Gateway is reachable, logout first stops the live WhatsApp listener for the selected account so the linked session does not keep receiving messages until the next restart. `openclaw channels remove --channel whatsapp` also stops the live listener before disabling or deleting account config.
In legacy auth directories, `oauth.json` is preserved while Baileys auth files are removed.
</Accordion>

2
docs/cli/channels.md
View File

@@ -52,6 +52,7 @@ openclaw channels remove --channel telegram --delete
</Tip>
`channels remove` only operates on installed/configured channel plugins. Use `channels add` first for installable catalog channels.
For runtime-backed channel plugins, `channels remove` also asks the running Gateway to stop the selected account before it updates config, so disabling or deleting an account does not leave the old listener active until restart.
Common non-interactive add surfaces include:
@@ -94,6 +95,7 @@ openclaw channels logout --channel whatsapp
- `channels login` supports `--verbose`.
- `channels login` and `logout` can infer the channel when only one supported login target is configured.
- `channels logout` prefers the live Gateway path when reachable, so logout stops any active listener before clearing channel auth state. If a local Gateway is not reachable, it falls back to local auth cleanup.
- Run `channels login` from a terminal on the gateway host. Agent `exec` blocks this interactive login flow; channel-native agent login tools, such as `whatsapp_login`, should be used from chat when available.
## Troubleshooting