The add-ons
Agent Channels
Every AgentSky agent answers on nine channels — Web, API, Slack, Telegram, Discord, WhatsApp, iMessage, CLI, and the A2A protocol. The agent, its workspace, and its state follow the conversation across all of them. Add a channel right on the call.
All nine channels — all live
Web
Chat with your agent in the AgentSky workspace from any browser. No setup — available the moment you create an agent.
API
Send messages and stream responses programmatically. The same API call that runs the agent also routes your message to it.
Slack
Each agent gets its own dedicated #channel in your Slack workspace. One-click connection per agent.
Telegram
Connect once at the account level and every agent answers in the same bot. Switch between agents with /name.
Discord
Each agent gets a dedicated #channel in your Discord server. Authorize once per server, add each agent in one click.
Message your agents directly from WhatsApp. Same number your team already uses — no separate app.
iMessage
Text your agents from Messages on iPhone or Mac. Works from both devices without any additional configuration.
CLI
Run the sky CLI to interact with your cloud agent directly from the terminal. Pipe output, pass files, script workflows.
A2A protocol
Expose your agent as an A2A server so other agents and orchestrators can delegate tasks to it over the open standard.
How you turn it on: add a channel right on the API call — no separate product, no extra dashboard. Open the Channels tab in your workspace and connect in one click. The agent picks up the connection immediately; no restart needed.
One agent, every surface
The agent follows the conversation across channels.
The workspace — running tasks, files, memory, active connectors — belongs to the agent instance, not to the channel you messaged it on. Start a task over the API, check its status in Telegram, review the output in Slack. You are not starting a new session each time; you are reaching the same running agent through a different surface.
Channels are routing, not identity. The agent and its state are always the source of truth.
Shared workspace
Files, memory, and in-progress tasks are visible no matter which channel the next message arrives on.
Crash-resilient
The agent keeps running after you close the browser tab or disconnect from the CLI. It surfaces the result on whichever channel you check next.
Zero-config switching
No re-authentication per channel. Connect a channel once; the agent answers there from that moment on.
Common questions
Nine channels, one agent