openclaw - 💡(How to fix) Fix [Feature Request] Cross-channel session continuity for named agents [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#68628Fetched 2026-04-19 15:09:21
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0

Error Message

  • Forces users to repeat context, which is frustrating and error-prone

Fix Action

Fix / Workaround

Expected behavior:

  1. Same agent on different channels (webchat, Telegram, etc.) should share the same session history
  2. When a user moves from webchat to Telegram, the agent should be able to continue the previous conversation seamlessly
  3. This should be the default behavior, not a workaround

Current workaround:

  • Rely on the main agent (which has MEMORY.md access) to store and retrieve context
  • Manually tell sub-agents what was discussed on other channels
RAW_BUFFERClick to expand / collapse

Problem: When a user switches from webchat to Telegram (or any other channel) while using the same named agent (e.g. "shigong"), the session history is not shared. The agent cannot see what was discussed on other channels in the same session, making it feel like a completely different conversation.

Expected behavior:

  1. Same agent on different channels (webchat, Telegram, etc.) should share the same session history
  2. When a user moves from webchat to Telegram, the agent should be able to continue the previous conversation seamlessly
  3. This should be the default behavior, not a workaround

Current workaround:

  • Rely on the main agent (which has MEMORY.md access) to store and retrieve context
  • Manually tell sub-agents what was discussed on other channels

Why this matters:

  • Poor user experience when switching between devices/channels
  • Breaks the illusion of talking to "one assistant" across multiple interfaces
  • Forces users to repeat context, which is frustrating and error-prone

Additional issue: Session compaction destroys conclusions and results When compaction runs, it truncates the session to a bootstrap summary and destroys all intermediate conclusions, final results, and output that was generated during the conversation. Only the bootstrap context is preserved. This means:

  • A task completed successfully? The result is gone after compaction
  • A file was generated? The agent cant recall it after compaction
  • A decision was made? Only the decision remains, not the context behind it
  • Compaction should preserve conclusions, results, and outputs — not just bootstrap metadata

Proposed solution options:

  1. Session key should NOT include the channel name for direct messages — use agent:{id}:direct:{userId} instead of agent:{id}:{channel}:direct:{userId}
  2. Add a configuration option to enable cross-channel session sharing per agent
  3. Default to shared session for same agent + same user, regardless of channel
  4. Improve compaction to preserve conclusions, results, and outputs rather than destroying all intermediate content

Label: enhancement, user-experience, session-management

extent analysis

TL;DR

Modify the session key to exclude the channel name for direct messages, using a format like agent:{id}:direct:{userId}, to enable cross-channel session sharing.

Guidance

  • Review the proposed solution options to determine the best approach for implementing cross-channel session sharing, considering factors like agent configuration and user experience.
  • Consider modifying the session compaction process to preserve conclusions, results, and outputs, rather than just bootstrap metadata, to improve the overall conversation history.
  • Evaluate the impact of changing the session key format on existing conversations and user data, to ensure a smooth transition.
  • Assess the need for a configuration option to enable cross-channel session sharing per agent, to provide flexibility and control.

Example

No code snippet is provided, as the issue focuses on conceptual changes to session management and compaction.

Notes

The solution may require significant changes to the underlying session management and compaction mechanisms, and may have implications for data storage and retrieval. It is essential to carefully evaluate the proposed solutions and consider potential edge cases and limitations.

Recommendation

Apply workaround: Modify the session key format to enable cross-channel session sharing, as this approach addresses the primary issue and provides a foundation for further improvements to session management and compaction.

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…

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 [Feature Request] Cross-channel session continuity for named agents [1 participants]