Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: sessions_list does not surface group sessions for the same agent [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59933•Fetched 2026-04-08 02:38:39
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
fattchrisfattchris
Participants
fattchrisfattchris

sessions_list returns only DM sessions even when active group sessions exist with messages and responses. This causes agents to believe group messages are not being received, leading to misdiagnosis during setup.

This is distinct from #53783 (cross-agent visibility) and #50478 (Discord channel scoping). This is same-agent, same instance — group session files exist on disk with valid messages, but sessions_list does not return them.

Root Cause

During initial group chat setup, this made it appear that group messages were not being received at all. The agent spent ~15 minutes troubleshooting a non-existent problem because the diagnostic tool was hiding the evidence that groups were working. This is a significant new-user friction point.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

sessions_list returns only DM sessions even when active group sessions exist with messages and responses. This causes agents to believe group messages are not being received, leading to misdiagnosis during setup.

This is distinct from #53783 (cross-agent visibility) and #50478 (Discord channel scoping). This is same-agent, same instance — group session files exist on disk with valid messages, but sessions_list does not return them.

Steps to reproduce

  1. Configure a Telegram bot with groupPolicy: "open" or allowlisted groups
  2. Send messages in both DM and a group chat
  3. Run sessions_list from the agent
  4. Observe: only the DM session is returned
  5. Manually inspect session .jsonl files — group sessions exist with messages and responses

Expected behavior

sessions_list should return all active sessions including group sessions, or at minimum support a filter like kinds: ["group"] that surfaces them.

Actual behavior

Only DM sessions are returned. Group sessions are invisible via the tool, requiring manual file inspection to discover.

Impact

During initial group chat setup, this made it appear that group messages were not being received at all. The agent spent ~15 minutes troubleshooting a non-existent problem because the diagnostic tool was hiding the evidence that groups were working. This is a significant new-user friction point.

Environment

  • OpenClaw version: AgentiMolt (current as of 2026-03-31)
  • Channel: Telegram
  • Chat type: Group
  • Agent: Dave (@internetdavebot_molt_bot)
  • Reported by: Devin Villegas

Related issues

  • #53783 (cross-agent group session visibility)
  • #50478 (sessions_list scoped to current session in Discord)

extent analysis

TL;DR

Modify the sessions_list function to include group sessions or add a filter to support retrieving group sessions.

Guidance

  • Verify that the groupPolicy is correctly set to "open" or that the groups are properly allowlisted in the Telegram bot configuration.
  • Check the implementation of sessions_list to ensure it is not explicitly filtering out group sessions.
  • Consider adding a filter parameter to sessions_list, such as kinds: ["group"], to allow agents to retrieve group sessions.
  • Inspect the session .jsonl files to confirm that group sessions are being written to disk correctly.

Example

No code snippet is provided as the issue does not include specific implementation details.

Notes

The solution may depend on the internal implementation of sessions_list and the Telegram bot configuration. Further investigation into the code and configuration is necessary to determine the root cause.

Recommendation

Apply a workaround by modifying the sessions_list function to include group sessions or adding a filter to support retrieving group sessions, as the current implementation is causing significant new-user friction.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

sessions_list should return all active sessions including group sessions, or at minimum support a filter like kinds: ["group"] that surfaces them.

#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: sessions_list does not surface group sessions for the same agent [1 participants]