Skip to content

The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.

docs(channels): clarify provider-dependent feature support

Steven Enamakelee66d16ed042
diff --git a/crates/openhuman-core/src/platform/about_app/catalog_auth_channels_team.rs b/crates/openhuman-core/src/platform/about_app/catalog_auth_channels_team.rs
index 053ee56698..7f693ff081 100644
--- a/crates/openhuman-core/src/platform/about_app/catalog_auth_channels_team.rs
+++ b/crates/openhuman-core/src/platform/about_app/catalog_auth_channels_team.rs
@@ -148,7 +148,7 @@ Capability {
name: "Connect Messaging Platforms",
domain: "channels",
category: CapabilityCategory::Channels,
- description: "Connect supported messaging platforms such as Telegram or Discord.",
+ description: "Connect supported messaging platforms such as Telegram or Discord. Threads, reactions, typing indicators, media, and voice depend on each configured provider's declared capabilities.",
how_to: "Connections > Channels",
status: CapabilityStatus::Beta,
privacy: None,
diff --git a/docs/gitbooks/en/features/channels.md b/docs/gitbooks/en/features/channels.md
index ad357a6c1b..27b2c69c32 100644
--- a/docs/gitbooks/en/features/channels.md
+++ b/docs/gitbooks/en/features/channels.md
@@ -67,7 +67,7 @@ OpenHuman has 15 channel providers. 14 are built into the shipped desktop app. W
WhatsApp also has an experimental peer-to-peer variant behind the `whatsapp-web` feature. Channels that use a webhook receive messages by HTTP push, so they need an HTTPS endpoint that the provider can reach.
-Telegram has the most features. It supports typing indicators and live draft updates, and it is the only channel with its own approval surface, so approval prompts can be answered inline. Discord adds native threaded replies, and Lark threads too. Web supports rich text and stays entirely local.
+Telegram has the most features. It supports typing indicators and live draft updates, and it is the only channel with its own approval surface, so approval prompts can be answered inline. Discord adds native threaded replies. Media, voice, and addressing support varies by provider and configured capabilities. Web supports rich text and stays entirely local.
### Email
diff --git a/docs/gitbooks/en/features/chat.md b/docs/gitbooks/en/features/chat.md
index 88ab6e75e7..4290519298 100644
--- a/docs/gitbooks/en/features/chat.md
+++ b/docs/gitbooks/en/features/chat.md
@@ -74,7 +74,7 @@ A thread can carry a goal and a to-do list that the agent sets. They show as a p
A long conversation is compacted, not truncated. Compaction seals what came before and starts a new generation that points back to the sealed one. Nothing is deleted on disk, though the model reads only the latest generation. There is no UI for browsing older generations yet.
-Chat attachments travel as typed content parts. The core keeps uploaded bytes
+In Web chat, attachments travel as typed content parts. The core keeps uploaded bytes
behind scoped opaque references in the durable user row; local file paths and
base64 data are not used as the persisted message reference. When a turn runs,
the trusted host resolves those references and passes the supported image,