Feature Request: Shared sessions across multiple group/channel chats
✅Solved
Use case:
Running an agent swarm where the same agent (Kevin) is bound to multiple Discord channels (#kevin-general, #kevin-ops). Currently, each channel gets an isolated session, so Kevin in channel A has zero context of discussions that happened in channel B.
This caused a real problem today: Kevin in one channel researched a tool with me for an hour, then Kevin in another channel (same agent, different session) contradicted everything because it had no context.
What I'd like:
Something like channelGroups or groupScope that works like dmScope: main but for channels:
{
session: {
channelGroups: {
"kevin-unified": [
"discord:channel:123456",
"discord:channel:789012"
]
}
}
}
Or even simpler, a groupScope: main that collapses all group/channel chats to the main session (opt-in, obviously).
Current workarounds considered:
Consolidate to a single channel (loses organisation)
Manual cross-session sync via sessions_send (error-prone)
Pre-response context injection from other sessions (adds latency)
Is there an existing way to achieve this that I'm missing? Or is this something that could be added?
@Krill 🦐
Running an agent swarm where the same agent (Kevin) is bound to multiple Discord channels (#kevin-general, #kevin-ops). Currently, each channel gets an isolated session, so Kevin in channel A has zero context of discussions that happened in channel B.
This caused a real problem today: Kevin in one channel researched a tool with me for an hour, then Kevin in another channel (same agent, different session) contradicted everything because it had no context.
What I'd like:
Something like channelGroups or groupScope that works like dmScope: main but for channels:
{
session: {
channelGroups: {
"kevin-unified": [
"discord:channel:123456",
"discord:channel:789012"
]
}
}
}
Or even simpler, a groupScope: main that collapses all group/channel chats to the main session (opt-in, obviously).
Current workarounds considered:
Consolidate to a single channel (loses organisation)
Manual cross-session sync via sessions_send (error-prone)
Pre-response context injection from other sessions (adds latency)
Is there an existing way to achieve this that I'm missing? Or is this something that could be added?
@Krill 🦐
Solution
…then all inbound chats (DMs + channels + groups across the whole gateway) share the single
(Confirmed by the session-key resolution logic + docs: https://docs.openclaw.ai/concepts/session and https://docs.openclaw.ai/web/tui)
- Use Memory as the shared brain: have “Kevin” write conclusions to
Docs: https://docs.openclaw.ai/concepts/memory
If you want this to be more automatic, you can also look at the experimental session transcript indexing mentioned there (
- Automated sync using session tools: still separate sessions, but you can standardize a “post summary to the other channel” step (less error-prone than manual).
Best next step: open a GitHub feature request with your exact proposed config shape + the concurrency/leakage expectations (same members vs different audiences). Repo issues: https://github.com/openclaw/openclaw/issues
global#kevin-general#kevin-ops(Confirmed by the session-key resolution logic + docs: https://docs.openclaw.ai/concepts/session and https://docs.openclaw.ai/web/tui)
Practical workarounds that don’t merge sessions
- Use Memory as the shared brain: have “Kevin” write conclusions to
memory/YYYY-MM-DD.mdDocs: https://docs.openclaw.ai/concepts/memory
If you want this to be more automatic, you can also look at the experimental session transcript indexing mentioned there (
memorySearch.experimental.sessionMemorymemory_search- Automated sync using session tools: still separate sessions, but you can standardize a “post summary to the other channel” step (less error-prone than manual).
If you want this as a real feature
What you’re describing makes sense as a routing/session-key alias layer (e.g. “these specific channel IDs map to the same sessionKey”). I don’t think there’s a config surface for that today for Discord.Best next step: open a GitHub feature request with your exact proposed config shape + the concurrency/leakage expectations (same members vs different audiences). Repo issues: https://github.com/openclaw/openclaw/issues
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Was this page helpful?
