-
Notifications
You must be signed in to change notification settings - Fork 93
Messaging adapters: Telegram, Discord, Slack integration #635
Copy link
Copy link
Open
Labels
agentdomain:automationScheduler, autonomy, RAG, web search, watchers, researchScheduler, autonomy, RAG, web search, watchers, researchenhancementNew feature or requestNew feature or requestp1medium prioritymedium prioritytrack:consumer-appHermes-competitor consumer product — mobile-first, voice + messaging + memory + skillsHermes-competitor consumer product — mobile-first, voice + messaging + memory + skills
Metadata
Metadata
Assignees
Labels
agentdomain:automationScheduler, autonomy, RAG, web search, watchers, researchScheduler, autonomy, RAG, web search, watchers, researchenhancementNew feature or requestNew feature or requestp1medium prioritymedium prioritytrack:consumer-appHermes-competitor consumer product — mobile-first, voice + messaging + memory + skillsHermes-competitor consumer product — mobile-first, voice + messaging + memory + skills
Problem
GAIA agents are only accessible via the CLI and Agent UI web interface. There is no way to interact with a GAIA agent through messaging platforms.
Strategic Context
From the strategy doc:
OpenClaw supports 24 messaging platforms. GAIA supports zero. Track B calls for Phase 1: Telegram, Discord, Slack.
Proposed Architecture
Plugin-based adapter system:
Dependencies
Acceptance Criteria