openclaw - 💡(How to fix) Fix Feature Request: Cross-channel session context sharing for the same agent [1 participants]

Feature Request: Cross-channel session context sharing for the same agent

Problem

When the same agent (e.g., agent:main) is accessed from multiple channels (webchat, WeChat, Telegram, etc.), each channel maintains its own independent session. This means:

• Webchat session: agent:main:main - has full conversation history
• WeChat session: g-agent-main-main - starts fresh when session resets

If a user discusses something in webchat, then asks via WeChat, the agent has no memory of the previous conversation.

Use Case

User is working on a project (discussed in webchat). Later, they ask about the project status via WeChat - the agent cannot recall the previous discussion because it's a different session.

Proposed Solution

Option 1: Allow binding sessions to a unified context pool

• Same agent across channels shares a common memory/context layer
• When session resets on any channel, restore context from shared memory

Option 2: Automatic context sync on session reset

• When a channel session resets, automatically restore context from shared memory file
• Provide a mechanism to define what context should be preserved (e.g., a shared-memory.md file)

Option 3: Built-in shared memory API

• Expose an API/endpoint that allows agents to read/write a shared context
• Could be file-based (~/.openclaw/agents/{agentId}/shared-memory.md) or database-backed

Priority

Medium-High - This is critical for multi-channel deployments where users expect consistent context across platforms.