---
title: "Supported message channels"
description: "Reach Orylo through iMessage, Telegram, Discord, WeChat, Slack, or Feishu/Lark—with explicit chat authorization."
locale: "en"
canonical: "https://orylo.io/en/docs/message-channels"
product_status: "in-development"
last_reviewed: "2026-10-05"
---

# Supported message channels

Reach Orylo through iMessage, Telegram, Discord, WeChat, Slack, or Feishu/Lark—with explicit chat authorization.

<a id="supported-channels"></a>

## Choose a channel

Open Settings → Remote → Messages. Each channel has its own switch and connection setup; it does not require Remote Web to be enabled. Your Mac must stay awake, connected, and running Orylo.

These are implemented channel integrations in the current Mac build, not a promise of universal platform availability. Provider policies, regional access, app installation, and permissions still apply. Verify setup and an actual round-trip with your own account.

| Channel | Setup | Conversation scope |
| --- | --- | --- |
| iMessage | Use Messages on this Mac, install the optional Orylo helper when prompted, and grant the required macOS permissions. | Explicitly connected one-to-one chats; it is not an inbox of all your Messages history. |
| Telegram | Add your bot credentials securely in the Mac settings; polling is used, not a webhook. | Approved bot direct messages; multiple bots can be configured. |
| Discord | Install your bot and enter its credentials securely; users must be able to message it. | Approved bot direct messages, not server-channel or group messages; multiple bots are supported. |
| Personal WeChat | Use the native iLink QR sign-in and confirm it in WeChat. | Authorized private chats, not WeChat groups; replies require a valid recent inbound context. |
| Slack | Install your Slack app with the required scopes/events and Socket Mode; Connect with Chat can help prepare the configuration. | Approved direct messages, plus explicitly approved channel @mentions with separate conversation threads. |
| Feishu / Lark | Configure the app’s permissions, events, credentials, and long connection for the correct region. | Approved private chats; platform or organization approval may be required. |

<a id="connect-chat"></a>

## Connect and verify one chat

Messages from an authorized chat use its linked native Orylo conversation. Changing the link does not rewrite the old history, and old chat history is not imported or replayed as fresh tasks. Use the channel’s help to see supported conversation-management commands; Slack private commands use the /orylo prefix.

1. **Prepare the channel** — Use its native setup for a token field or QR sign-in. For multi-step app permissions, installation, or diagnostics, choose Connect with Chat. Enter secrets only in secure native fields, not in the conversation.
2. **Authorize the intended contact** — For bot pairing, send a private message and compare the returned pairing code with the request on the Mac before approving. For iMessage, use its native new-chat flow. Select or create the intended Orylo conversation and confirm the Assistant and workspace.
3. **Send a fresh test request** — The initial bot pairing message is not executed or replayed as a task. After authorization, send a new harmless request and check the final reply. A connected transport or a successful test send does not prove the Agent can complete work.

<a id="slack-threads"></a>

## Slack channel mentions are an explicit exception

After you approve a Slack channel on the Mac, any member of that channel can invoke Orylo with an @mention. Each thread gets its own native conversation, and replies stay in that thread. Decide whether that channel-wide access is appropriate before approving it.

Orylo does not import channel history or send ordinary channel messages or unmentioned thread replies to the Agent. A channel thread cannot be linked to an existing conversation and does not accept private-chat management commands. Disconnecting one thread revokes that bot’s connections for the whole channel; native history is preserved.

Slack may require broader platform scopes than Orylo’s message-processing rules. Orylo can fetch a single thread-root message to label the thread; it does not pass that root message to the Agent as context. Review the app’s actual requested permissions before installation.

<a id="privacy-and-limits"></a>

## Know what crosses the channel

Channels deliver final text replies rather than token-by-token output. Supported incoming attachments depend on the channel and the Assistant; a failed required attachment rejects the input rather than silently sending its caption alone. Do not assume every native attachment or rich result can be delivered back through every platform.

Message channels do not grant automatic approval for Agent permission requests. Complete unsupported approvals on the Mac; an ordinary “yes” message is not permission to bypass them. Use Remote Web when you need its supported interactive controls.

Only authorized chats are connected, but messages you send and replies delivered through a platform also pass through that platform. Orylo’s local-first storage does not make an external message service local or guarantee end-to-end encryption. Disabling a channel stops that entry, not the native Mac app or all its tasks.

## Continue exploring

- [Set up Remote Access](https://orylo.io/en/docs/remote-access)
- [Work in Remote Web](https://orylo.io/en/docs/remote-web)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Permissions & control](https://orylo.io/en/docs/permissions)