Universal Memory Gap: Discord & Telegram conversations not committed to the agent's memory

Labels

bug
architecture
memory-system
high-priority
discord
telegram
Body

🚨 Problem Statement

All messaging adapters (Discord, Telegram, webchat) successfully process messages and agents generate responses, but conversations are NOT committed to the agents memory system.

Impact

• ❌ Loss of context across platform switches (Telegram → Webchat = no recall)
• ❌ No cross-session persistence within platforms
• ❌ Discord conversations invisible to Telegram context
• ❌ Prevents true multi-platform coordination

---

🧪 Evidence from Both Platforms

Discord Integration

• ✅ Status: Working (bot online, responds to @mentions, 12 channel bindings configured)
• ❌ Memory: NO Discord conversations appear in agent memory
• 🔍 Test: User asks question in Discord #heads → agent responds → User asks same topic in Webchat → agent has zero memory: "I don't have context from Discord"

Telegram Integration

• ✅ Status: Working (bot responds, single-bot configuration successful)
• ❌ Memory: NO Telegram conversations appear in agent memory
• 🔍 Test: User messages bot in Telegram → Nexus responds with personality → Webchat query about Telegram conversation → agent cannot recall: "What Telegram conversation?"

Webchat Integration

• ✅ Status: Working (primary channel, all messages route correctly)
• ✅ Memory: Working (our current conversation is resident in memory)
• Note: Webchat appears to have implicit memory_save() lifecycle hooks

---

🔍 Root Cause Analysis

Current Message Flow (Broken)

User Message → Adapter → Agent → Response Sent ↓ ❌ NO memory_save() call

Required Message Flow (Fixed)

User Message → Adapter → Agent → Response Sent ↓ ✅ memory_save() → agent Cortex → Persistent Storage

Adapters lack memory_save() hooks after agent responses complete. The Discord, Telegram, and (likely) other adapters commit to agent cortex processing but do not persist the conversation transcript to long-term memory.

---

🎯 Platform-Specific Architecture Context

Discord: Multi-Bot Required

• Architecture: Each agent needs distinct bot identity (agent#3891, pm-ten-offset-yield, etc.)
• Routing: @mentions route to specific bot users
• Tokens: Multiple bot tokens required
• Status: ✅ Multi-bot architecture implemented, working

Telegram: Single-Bot Router

• Architecture: One bot (@ConvergenceBot) with slash command routing
• Routing: Commands /nexus, /offset, /orchestrator route to agents
• Tokens: Single bot token sufficient
• Status: ✅ Single bot working, default routing functional

Common Gap

Both architectures successfully route messages but neither commits conversations to agent memory.

Trace the Discord and Telegram messaging adapters through agent response handling, then compare their lifecycle with webchat's memory_save() behavior. Verify where conversations enter agent Cortex and persistent storage. Done means Discord and Telegram transcripts are persisted and can be recalled across platforms and sessions.