Turn any machineinto a chat bot
Telegram, Discord, Slack — powered by the same cmdop SDK core. One install, a few lines, and every message reaches your machines through machines.ask.
Three channels,one runtime
The same bot loop speaks every channel. Pick where your team already talks — the SDK handles the rest.
Bot API token in, replies out. DMs and groups.
Slash commands and channel messages, gateway-native.
App mentions and DMs across your workspace.
Start a bot,the binary runs the loop
You call client.bots.run(...) and the Go core takes over: it listens on the channel and, per message, calls the SDK’s own machines.ask. No new endpoint, no server to host.
Bots, the SDK way
Built into the SDK core
Bots are not a separate library you install and wire up. They are a first-class op on the same client you already use for machines, fleets and tunnels — client.bots.run, and you are live.
Runs entirely in the Go binary
The Telegram, Discord and Slack event loops live inside cmdop-core. There is no Python or Node process babysitting a websocket — the baked-in binary owns the channel, so it survives, retries and reconnects on its own.
Every message becomes machines.ask
Each chat message is forwarded to your machine’s AI agent through the relay’s streaming machines.ask, with the same pin/confirm guarantees. The bot is a pure consumer of the machine surface you already trust.
One install, every channel
pip install cmdop or npm i @cmdop/sdk ships all five platform binaries baked in. No extra bot SDK, no per-channel dependency — switch from Telegram to Slack by changing one argument.
Bots stand on the cmdop SDK
Everything a bot can do, the SDK can do — bots are just the chat-channel front door. Start with the SDK and add a bot in a few lines.
Turn a machine into a bot today
Install the SDK, call client.bots.run, and your fleet answers in Telegram, Discord or Slack.