Today conversation keys are fixed per trigger: Discord keys per channel/thread, Slack per thread, Telegram per chat, webhook per conversation_id. In a group channel that means everyone shares one rolling conversation with the agent.
Make this configurable, so an agent can be run either way:
- group (current behaviour): one shared conversation per channel/thread/chat; the agent sees the room's context
- individual: one conversation per user, even inside a group chat, so each person gets their own session and memory
Sketch:
memory:
scope: thread
key: channel | user # or per-trigger override
Open questions:
- Does the key belong on
memory: or per trigger?
- In individual mode, what does the agent see of other users' messages in the same channel?
- How this interacts with
from_users filters and observer agents
🤖 Generated with Claude Code
Today conversation keys are fixed per trigger: Discord keys per channel/thread, Slack per thread, Telegram per chat, webhook per
conversation_id. In a group channel that means everyone shares one rolling conversation with the agent.Make this configurable, so an agent can be run either way:
Sketch:
Open questions:
memory:or per trigger?from_usersfilters and observer agents🤖 Generated with Claude Code