Skip to content

Open-source AI teammates in Slack, Teams, Discord, Telegram and Mattermost. Self-host it, with any agent harness and any model.

docs(skills): Telegram has no DM, so stop telling agents to wait for one (#278)

Louis Amaudruzdb7dc85543ce
diff --git a/CHANGELOG.md b/CHANGELOG.md
index cef73499b..4b01954df 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -699,6 +699,11 @@ version of their own to them without also giving them a release of their own.
## switch-console
### [Unreleased]
+#### Fixed
+- The OpenCode connector the app writes carries its own copy of the
+ room-workflow skill, so it picked up the same wrong claim that a Telegram DM
+ is adopted like Mattermost's. Corrected alongside the connector directory
+ (CHOO-2314).
#### Changed
- Every **Docs** affordance opens the published documentation at
@@ -2185,6 +2190,13 @@ compatibility signal. History for those is in the git log.
`.claude-plugin/plugin.json`.
### [Unreleased]
+#### Fixed
+- The room-workflow skill said a Telegram DM is adopted the way Mattermost's
+ is, so an agent asked for a 1:1 on Telegram would tell the user to message
+ the bot and wait for a room that never arrives. Telegram has no DM: a private
+ chat with the bot is the lobby, which answers with setup guidance and
+ provisions nothing. The skill now says so, and points at a group of two as
+ the way to get DM-like behaviour (CHOO-2314).
### [0.9.6] - 2026-08-19
@@ -2379,6 +2391,13 @@ manifest history.
`connectors/codex-plugin/`. Version lives in `.codex-plugin/plugin.json`.
### [Unreleased]
+#### Fixed
+- The room-workflow skill said a Telegram DM is adopted the way Mattermost's
+ is, so an agent asked for a 1:1 on Telegram would tell the user to message
+ the bot and wait for a room that never arrives. Telegram has no DM: a private
+ chat with the bot is the lobby, which answers with setup guidance and
+ provisions nothing. The skill now says so, and points at a group of two as
+ the way to get DM-like behaviour (CHOO-2314).
### [0.3.7] - 2026-08-19
@@ -2527,6 +2546,13 @@ for humans reading a diff rather than for an installer, and an install reports
the app version that wrote it rather than a version of its own.
### [Unreleased]
+#### Fixed
+- The room-workflow skill said a Telegram DM is adopted the way Mattermost's
+ is, so an agent asked for a 1:1 on Telegram would tell the user to message
+ the bot and wait for a room that never arrives. Telegram has no DM: a private
+ chat with the bot is the lobby, which answers with setup guidance and
+ provisions nothing. The skill now says so, and points at a group of two as
+ the way to get DM-like behaviour (CHOO-2314).
### [0.1.4] - 2026-08-19
diff --git a/connectors/claude-code-plugin/skills/switch/SKILL.md b/connectors/claude-code-plugin/skills/switch/SKILL.md
index 4ea4f25d3..9f469179f 100644
--- a/connectors/claude-code-plugin/skills/switch/SKILL.md
+++ b/connectors/claude-code-plugin/skills/switch/SKILL.md
@@ -450,14 +450,20 @@ For a private 1:1 between one agent and one human, create a room with
- **Mattermost**: DMs are user-initiated from the client, so creating a
`direct` room here fails — the user starts the DM with the agent's bot and
Switch picks it up automatically.
-- **Telegram**: same as Mattermost — the user messages the bot first and
- Switch adopts the chat. Telegram bots cannot create chats at all, so
- `create_room` fails on a Telegram bridge for *every* channel type, not just
- `direct`; the chat is made in a Telegram client and the bot added to it.
- `list_bridges` reports this as `can_create_channels: false`, so check there
- before offering to make a room rather than finding out from the failure —
- and note an operator can withhold channel creation from any platform, so a
- false answer is not Telegram-specific.
+- **Telegram**: there is **no DM at all**, and this one is not a "create it
+ from the other side" case. A private chat with the bot is the *lobby*: the
+ bridge answers it with setup guidance and never provisions a room, so no
+ agent is reachable there and nothing you do in Telegram adopts it. One bot
+ fronts every agent, so a 1:1 could not say which agent it was with anyway.
+ Offer a **group containing just that user and the bot**, with the one agent
+ invited — that behaves like a DM and the agent is addressable by name.
+ Separately, Telegram bots cannot create chats at all, so `create_room` fails
+ on a Telegram bridge for *every* channel type, not just `direct`; the chat is
+ made in a Telegram client and the bot added to it. `list_bridges` reports
+ this as `can_create_channels: false`, so check there before offering to make
+ a room rather than finding out from the failure — and note an operator can
+ withhold channel creation from any platform, so a false answer is not
+ Telegram-specific.
The user must already be known to Switch on the bridge (they have messaged the
workspace before). If not, creation fails loudly with `no user '<name>' is
diff --git a/connectors/codex-plugin/skills/switch/SKILL.md b/connectors/codex-plugin/skills/switch/SKILL.md
index cb5793a78..b577f9183 100644
--- a/connectors/codex-plugin/skills/switch/SKILL.md
+++ b/connectors/codex-plugin/skills/switch/SKILL.md
@@ -448,14 +448,20 @@ For a private 1:1 between one agent and one human, create a room with
- **Mattermost**: DMs are user-initiated from the client, so creating a
`direct` room here fails — the user starts the DM with the agent's bot and
Switch picks it up automatically.
-- **Telegram**: same as Mattermost — the user messages the bot first and
- Switch adopts the chat. Telegram bots cannot create chats at all, so
- `create_room` fails on a Telegram bridge for *every* channel type, not just
- `direct`; the chat is made in a Telegram client and the bot added to it.
- `list_bridges` reports this as `can_create_channels: false`, so check there
- before offering to make a room rather than finding out from the failure —
- and note an operator can withhold channel creation from any platform, so a
- false answer is not Telegram-specific.
+- **Telegram**: there is **no DM at all**, and this one is not a "create it
+ from the other side" case. A private chat with the bot is the *lobby*: the
+ bridge answers it with setup guidance and never provisions a room, so no
+ agent is reachable there and nothing you do in Telegram adopts it. One bot
+ fronts every agent, so a 1:1 could not say which agent it was with anyway.
+ Offer a **group containing just that user and the bot**, with the one agent
+ invited — that behaves like a DM and the agent is addressable by name.
+ Separately, Telegram bots cannot create chats at all, so `create_room` fails
+ on a Telegram bridge for *every* channel type, not just `direct`; the chat is
+ made in a Telegram client and the bot added to it. `list_bridges` reports
+ this as `can_create_channels: false`, so check there before offering to make
+ a room rather than finding out from the failure — and note an operator can
+ withhold channel creation from any platform, so a false answer is not
+ Telegram-specific.
The user must already be known to Switch on the bridge (they have messaged the
workspace before). If not, creation fails loudly with `no user '<name>' is
diff --git a/connectors/opencode-plugin/skills/switch/SKILL.md b/connectors/opencode-plugin/skills/switch/SKILL.md
index 6b18ee2e4..6bee38c40 100644
--- a/connectors/opencode-plugin/skills/switch/SKILL.md
+++ b/connectors/opencode-plugin/skills/switch/SKILL.md
@@ -456,14 +456,20 @@ For a private 1:1 between one agent and one human, create a room with
- **Mattermost**: DMs are user-initiated from the client, so creating a
`direct` room here fails — the user starts the DM with the agent's bot and
Switch picks it up automatically.
-- **Telegram**: same as Mattermost — the user messages the bot first and
- Switch adopts the chat. Telegram bots cannot create chats at all, so
- `create_room` fails on a Telegram bridge for *every* channel type, not just
- `direct`; the chat is made in a Telegram client and the bot added to it.
- `list_bridges` reports this as `can_create_channels: false`, so check there
- before offering to make a room rather than finding out from the failure —
- and note an operator can withhold channel creation from any platform, so a
- false answer is not Telegram-specific.
+- **Telegram**: there is **no DM at all**, and this one is not a "create it
+ from the other side" case. A private chat with the bot is the *lobby*: the
+ bridge answers it with setup guidance and never provisions a room, so no
+ agent is reachable there and nothing you do in Telegram adopts it. One bot
+ fronts every agent, so a 1:1 could not say which agent it was with anyway.
+ Offer a **group containing just that user and the bot**, with the one agent
+ invited — that behaves like a DM and the agent is addressable by name.
+ Separately, Telegram bots cannot create chats at all, so `create_room` fails
+ on a Telegram bridge for *every* channel type, not just `direct`; the chat is
+ made in a Telegram client and the bot added to it. `list_bridges` reports
+ this as `can_create_channels: false`, so check there before offering to make
+ a room rather than finding out from the failure — and note an operator can
+ withhold channel creation from any platform, so a false answer is not
+ Telegram-specific.
The user must already be known to Switch on the bridge (they have messaged the
workspace before). If not, creation fails loudly with `no user '<name>' is
diff --git a/console/packages/plugins/src/agents/impl/opencode/skill-file.ts b/console/packages/plugins/src/agents/impl/opencode/skill-file.ts
index d440d8ca3..7bdb7c031 100644
--- a/console/packages/plugins/src/agents/impl/opencode/skill-file.ts
+++ b/console/packages/plugins/src/agents/impl/opencode/skill-file.ts
@@ -464,14 +464,20 @@ For a private 1:1 between one agent and one human, create a room with
- **Mattermost**: DMs are user-initiated from the client, so creating a
\`direct\` room here fails — the user starts the DM with the agent's bot and
Switch picks it up automatically.
-- **Telegram**: same as Mattermost — the user messages the bot first and
- Switch adopts the chat. Telegram bots cannot create chats at all, so
- \`create_room\` fails on a Telegram bridge for *every* channel type, not just
- \`direct\`; the chat is made in a Telegram client and the bot added to it.
- \`list_bridges\` reports this as \`can_create_channels: false\`, so check there
- before offering to make a room rather than finding out from the failure —
- and note an operator can withhold channel creation from any platform, so a
- false answer is not Telegram-specific.
+- **Telegram**: there is **no DM at all**, and this one is not a "create it
+ from the other side" case. A private chat with the bot is the *lobby*: the
+ bridge answers it with setup guidance and never provisions a room, so no
+ agent is reachable there and nothing you do in Telegram adopts it. One bot
+ fronts every agent, so a 1:1 could not say which agent it was with anyway.
+ Offer a **group containing just that user and the bot**, with the one agent
+ invited — that behaves like a DM and the agent is addressable by name.
+ Separately, Telegram bots cannot create chats at all, so \`create_room\` fails
+ on a Telegram bridge for *every* channel type, not just \`direct\`; the chat is
+ made in a Telegram client and the bot added to it. \`list_bridges\` reports
+ this as \`can_create_channels: false\`, so check there before offering to make
+ a room rather than finding out from the failure — and note an operator can
+ withhold channel creation from any platform, so a false answer is not
+ Telegram-specific.
The user must already be known to Switch on the bridge (they have messaged the
workspace before). If not, creation fails loudly with \`no user '<name>' is