Skip to content

Messaging adapters: Telegram, Discord, Slack integration #635

@kovtcharov

Description

@kovtcharov

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:

"Messaging is the interface, not an app. Adoption was driven by WhatsApp, Telegram, and Discord — not OpenClaw's web UI. Users want AI woven into existing tools."

OpenClaw supports 24 messaging platforms. GAIA supports zero. Track B calls for Phase 1: Telegram, Discord, Slack.

Proposed Architecture

Plugin-based adapter system:

  1. Adapter interface — Standard message receive/send contract
  2. Telegram adapter — Bot API integration (Phase 1)
  3. Discord adapter — Bot integration (Phase 1)
  4. Slack adapter — App integration (Phase 1)
  5. Message routing — Route incoming messages to appropriate agent, return responses

Dependencies

  • Agent API (OpenAI-compatible server, already exists)
  • Background service (NEW-8: autonomy engine)

Acceptance Criteria

  • User can text their GAIA agent on Telegram and get responses
  • Discord bot integration working
  • Slack app integration working
  • Standard adapter interface for community contributions

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentdomain:automationScheduler, autonomy, RAG, web search, watchers, researchenhancementNew feature or requestp1medium prioritytrack:consumer-appHermes-competitor consumer product — mobile-first, voice + messaging + memory + skills

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions