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

docs(health): clarify session list liveness

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 07:50:20 +01:00
parent 689986ccb7
commit 301a255ae7
4 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/cli/channels.md
View File

@@ -39,6 +39,12 @@ state plus probe results such as `works`, `probe failed`, `audit ok`, or `audit
If the gateway is unreachable, `channels status` falls back to config-only summaries
instead of live probe output.
Do not use `openclaw sessions`, Gateway `sessions.list`, or the agent
`sessions_list` tool as a channel socket-health signal. Those surfaces report
stored conversation rows, not provider runtime state. After a Discord provider
restart, a connected but quiet account may be healthy while no Discord session
row appears until the next inbound or outbound conversation event.
## Add / remove accounts
```bash

7
docs/cli/sessions.md
View File

@@ -9,6 +9,13 @@ title: "Sessions"
List stored conversation sessions.
Session lists are not channel/provider liveness checks. They show persisted
conversation rows from session stores. A quiet Discord, Slack, Telegram, or
other channel can reconnect successfully without creating a new session row
until a message is processed. Use `openclaw channels status --probe`,
`openclaw status --deep`, or `openclaw health --verbose` when you need live
channel connectivity.
```bash
openclaw sessions
openclaw sessions --agent work