Skip to content

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

docs(channels): update channel documentation

Steven Enamakele1a95b28e9ab
diff --git a/crates/openhuman-core/src/channels/README.md b/crates/openhuman-core/src/channels/README.md
index eb7d3024b1..2dc7dc61f9 100644
--- a/crates/openhuman-core/src/channels/README.md
+++ b/crates/openhuman-core/src/channels/README.md
@@ -17,9 +17,14 @@ module owns provider-specific startup, supervision, transport, and interaction
behavior; OpenHuman owns routing, approvals, agent execution, and the session
cancellation lifetime.
-The normal provider type and provider re-exports are available only to tests
-that retain legacy compatibility fixtures. Production code uses the portable
-TinyChannels bus contracts from `tinychannels-bus` and the module client.
+Production code uses the portable TinyChannels bus contracts from
+`tinychannels-bus` and the compiled module client. Provider algorithms,
+transports, and concrete adapters stay in TinyChannels; OpenHuman does not
+link the provider implementation library or expose a host-side provider trait.
+The module prepares inbound identity and typed content before the host applies
+its account authorization and session policy. Host callbacks handle only
+capabilities the module cannot own, such as scoped media access, voice, and
+event publication.
## Hosted and relay paths
@@ -47,7 +52,7 @@ or shell-based substitute.
| Path | Purpose |
| --- | --- |
-| [`mod.rs`](./mod.rs) | Feature gates and the public channel contract exports. Concrete provider exports are test-only. |
+| [`mod.rs`](./mod.rs) | Feature gates, TinyBus module setup, and host-facing channel contracts. |
| [`tinychannels-bus channel contracts`](../../../../vendor/tinychannels/crates/tinychannels-bus/src/channel/) | Portable message and typed send contracts. |
| [`controllers/`](./controllers/) | OpenHuman `channels.*` operations and host-side backend transport adaptation. |
| [`host/`](./host/) | Typed module callbacks, event subscribers, and remote-control host operations. |
diff --git a/docs/gitbooks/en/features/channels.md b/docs/gitbooks/en/features/channels.md
index 336fb11e8a..a56e1aa406 100644
--- a/docs/gitbooks/en/features/channels.md
+++ b/docs/gitbooks/en/features/channels.md
@@ -13,6 +13,10 @@ Channel providers normalize platform messages into typed envelopes and send
typed replies through the configured provider. OpenHuman keeps account policy,
authorization, agent execution, and durable conversation sessions in the host;
provider transport runs in the TinyChannels module behind its bus contract.
+The host communicates with the module through typed TinyBus requests and
+callbacks: it does not link provider implementations. The module prepares
+provider identity and ordered message parts; OpenHuman checks access, selects
+the agent, and binds the message to its durable session before running a turn.
## What a channel does
@@ -33,7 +37,11 @@ incoming message, when a [trigger](integrations/triggers.md) or cron job fires.
A channel receives proactive messages only if it has a default delivery
target. Channels without one are skipped.
-Where the platform allows it, channels can show a typing indicator, stream draft updates, post threaded replies and add emoji reactions. Each channel declares what it supports.
+Where the platform allows it, channels can show a typing indicator, stream
+draft updates, post threaded replies, send supported media or voice notes, and
+add emoji reactions. These are provider-specific capabilities: the module
+reports what each configured provider supports, and OpenHuman does not emulate
+an unsupported operation.
## Supported channels