Interfaces

Connect deployed agents to Slack, Discord, WhatsApp, Telegram, and protocols like A2A and AG-UI.

You’ve deployed your platform and added agents. Now connect them to where your users already are.

Interfaces let users interact with your agents through Slack, Telegram, WhatsApp, Discord, or your own frontend. Each interface handles user isolation, message threading, streaming, and platform-native formatting so you focus on the agent, not the plumbing.

Choose an Interface

Interface	Best For	Setup Time
Slack	Teams already on Slack	15 min
Telegram	Public bots, quick prototypes	5 min
WhatsApp	Customer messaging at scale	30 min
Discord	Gaming communities, public servers	10 min
AG-UI	Custom web/mobile frontends	Varies
A2A	Agent-to-agent communication	10 min

Messaging Platforms

Slack

Messages, threads, slash commands. Full setup guide with OAuth scopes.

Telegram

Messages, images, files, inline keyboards. Just a bot token to start.

WhatsApp

Messages, images, documents, audio. Business API with message templates.

Discord

Messages, threads, reactions, embeds. Client-based using discord.py.

Protocols

AG-UI

Streaming, generative UI, state sync. CopilotKit protocol.

A2A

Agent discovery, task delegation. Google protocol.

Prerequisites

Before connecting an interface:

1. Running AgentOS — Docker, Railway, or AWS
2. Public URL — Your AgentOS must be reachable from the internet
3. Platform credentials — Bot tokens, API keys, or OAuth apps (see each interface guide)

For local dev, expose localhost with ngrok, Cloudflare Tunnel, or localhost.run.

Next Steps

Tracing

Debug live conversations. See every LLM call and tool execution.

Scheduler

Automate with cron. Daily summaries, weekly reports, periodic checks.

Build Custom Agents

Go beyond templates. Create agents with your own tools and instructions.

Approvals

Gate dangerous operations with human-in-the-loop confirmation.