Channel integrations

Your agent talks to you through an external channel. Onepilot configures that channel for you in the app — pick one during deploy and it wires the bot — for both OpenClaw and Hermes.

TL;DR

Onepilot configures Telegram, Discord, or Slack for your OpenClaw or Hermesagent right in the app, so you don't hand-edit gateway configs over SSH. The agent runs on a host you own, and the same app gives you the real SSH cockpit — terminal, file browser, git, and cron — on top of the conversation. One app, multiple frameworks, the channel and the host together.

Configure your agent's channel in the app — one email when Onepilot ships on the App Store.

Pick a channel

TelegramVoice memos that auto-transcribe, group @mention gating, the most popular agent channel.DiscordA shared, channel-scoped agent for teams and communities, with threads to keep work tidy.SlackA work agent in DMs or channels, posting results where your team already is.

Why the channel lives in the app

Wiring a channel by hand means juggling bot tokens, user IDs or OAuth scopes, and the agent's gateway config over SSH. Onepilot collapses that into a wizard step: you bring the token, the app writes the config on the host and starts the bot. The channel layer is identical whether you run OpenClaw or Hermes, even though the frameworks differ underneath.

And because Onepilot connects over a real SSH tunnel rather than a browser WebUI, the conversation on your channel sits next to the host itself — terminal, files, git, cron — in one app.

Configure your agent's channel

Drop your email and we'll send one note when Onepilot ships on the App Store.