Skip to main content
GenosOS connects to every channel you already use. WhatsApp, Telegram, Slack, Discord, Signal, voice calls — they all route to the same assistant, with the same memory and context. You don’t manage separate bots. You have one assistant that happens to be everywhere.

​
How to connect any channel

You don’t edit config files. You tell your assistant what you want: 
You: "Connect my WhatsApp"
     → QR code overlay appears, you scan it, done.

You: "Connect Telegram"
     → Agent walks you through @BotFather in five steps.

You: "I want to receive phone calls"
     → Agent asks for your Twilio credentials and sets up the webhook.
The agent knows every setup step. You just follow the conversation.

​
Messaging channels

ChannelLibraryStatus
WhatsApp@whiskeysockets/baileysProduction
TelegramgrammYProduction
Slack@slack/boltProduction
Discorddiscord.js (@buape/carbon)Production
Signalsignal-utilsProduction
iMessagemacOS nativeProduction

​
Voice channels

ChannelTechnologyStatus
Voice CallsTwilio / Telnyx / Plivo + OpenAI Realtime STTProduction
Realtime CallOpenAI Realtime API (true bidirectional)Experimental
Local TTSKokoro (on-device, no cloud)Production

​
Additional channels

Google Chat, Microsoft Teams, Matrix, Nostr, Twitch, LINE, WebChat — available as optional extensions. Tell your assistant “I use Teams” or “I use LINE” to get started.

​
DM policy

Every channel has a DM policy that controls who can reach your assistant. The default is pairing — the safest option for a new setup.
PolicyBehavior
pairingUnknown senders receive an 8-character alphanumeric code. You approve each one.
allowlistOnly phone numbers or user IDs you specify can send messages.
openAnyone can message your assistant.
disabledThe channel ignores all incoming messages.
To change the policy conversationally: 
You: "Only let my contacts message me on WhatsApp"
You: "Open Telegram to anyone"
You: "Disable DMs on Discord"
The agent translates your intent into the correct configuration automatically.

​
Channel tool restrictions

Not all channels carry the same level of trust. GenosOS applies a deny-only security layer based on the channel that delivered the message:
Channel contextRestrictions
Web UI (localhost)None — full tool access
WhatsApp / Telegram / Discord / Signalexec, bash, process denied
Voice calls (inbound)Nearly all tools denied except session management
This means a message arriving through WhatsApp cannot trigger shell commands on your machine — even if the message asks for it. The restriction is architectural, not advisory. It applies regardless of what the message says.
You can still read files, search memory, send messages, and use web tools from messaging channels. Only shell execution is blocked.

​
Channel pages

WhatsApp

Connect via QR code scan. No token required.

Telegram

Create a bot via @BotFather and paste the token.

Slack

Socket Mode or HTTP mode with @slack/bolt.

Discord

Developer Portal bot token with Message Content Intent.

Signal

Requires signal-cli and a dedicated phone number.

Voice calls

Inbound and outbound calls with Twilio, Telnyx, or Plivo.