#How can I have multiple sessions?

1 messages Β· Page 1 of 1 (latest)

wide quest
#

I've linked telegram and also use your webui.
In your webui there's a new session button, but that seems to wipe the previous conversation/session.
Whatever I write in either telegram or your gateway dashboard is synced across each other.
I'd like to be able to have a conversation about one task/topic, then start a separate conversation about another at the same time without them conflicting or getting in the way of each other.

hollow tartanBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> βœ… Mark Solution

rocky bisonBOT
# wide quest I've linked telegram and also use your webui. In your webui there's a new sessio...

Based on the Clawdbot docs and architecture, here's the situation with sessions and how to achieve what you want:

How Sessions Currently Work

Clawdbot uses a single active session per channel model:

  • Multiple transports share one session β†’ Telegram + web UI for the same direct chat = same conversation
  • Group chats get their own isolated session keys automatically
  • The "New Session" button (/new or /reset) wipes the previous session to start fresh

Your Options for Separate Conversations

1. Use Different Channels/Groups 🟒 Easiest

Create separate Telegram groups or Discord channels for different topics. Each will have its own isolated session:

Telegram Group A β†’ session: agent:default:telegram:group:<id_A>
Telegram Group B β†’ session: agent:default:telegram:group:<id_B>
#

2. Create Multiple Agents 🟒 Cleanest

Set up separate agents in your config for different topics:

{
  agents: {
    "coding-agent": { /* ... */ },
    "personal-agent": { /* ... */ }
  }
}

Each agent has completely separate sessions.

3. Manual Session Switching (Advanced)

The web UI should support listing sessions via sessions_list tool. You can switch between existing sessions without wiping them. If the current web UI "New Session" button just does /reset, that's a UX gap.

What Needs to Change