Channel Integration
The Epistemic Memory Engine works across any channel supported by OpenClaw. Here's how to optimize for each platform.
Supported Channels
| Channel | Trust Level | Identity | Notes |
|---|---|---|---|
| Telegram DM | Full (1.0) | User ID | Primary channel for most users |
| Telegram Group | Reduced (0.5) | User ID | Channel isolation recommended |
| Zalo | Full (1.0) | Zalo ID | Use ownerAliases for unification |
| Discord | Full/Reduced | Discord ID | DM vs. server distinction |
| Matrix | Full (1.0) | Matrix ID | End-to-end encrypted rooms supported |
| IRC | Reduced (0.5) | Nick | No persistent identity — lower trust |
Identity Unification Setup
openclaw.json
{
"ownerId": "telegram:123456789",
"ownerAliases": [
"zalo:0901234567",
"discord:987654321",
"matrix:@huy:matrix.org"
]
}With this configuration, messages from any of these IDs will be treated as the owner's messages with full trust.
Channel Isolation
When channelIsolation: true:
- Group chat memories are tagged with the specific group ID
- Recall in a group only returns memories from that group + owner's DM memories
- DM recall returns all owner memories (bypasses isolation)
Telegram Tips
- Use
/memorycommands for quick health checks - Group admins can be added as trusted sources via configuration
- Bot messages in groups are automatically tagged as
agent_inferred
Multi-Channel Workflow
- Chat with the bot on Telegram — memories are stored with full trust
- Switch to Zalo — same memories available thanks to identity unification
- Join a Discord server — channel isolation keeps server-specific context separate
- All memories unified in a single knowledge graph regardless of channel