[FEATURE] Drive OpenCode from chat apps: official "agent as a bot" gateway (Telegram/Slack/webhook) — the OpenClaw-class gap

[liudongyan13701205717-source]

Feature request

OpenClaw/Hermes let you drive the coding agent from chat apps: you message your agent on Telegram/WhatsApp/Slack/WeChat and it executes in your workspace, then pushes the result back to chat. OpenCode only works when the terminal/desktop app is open and focused.

What we'd like

Classic "agent as a bot" mode for the desktop workflow:

1. A background opencode bot-style runtime (or an official start of the existing serve/attach):

   • starts daemon in the project dir,
   • listens to a chat connector (e.g. official Telegram bot via token), and/or exposes a standard API / webhook for third-party bridges (the community already bridges WeChat via ACP; make it official).
   • tasks come in via chat (damage/permission: same permissions system as local), replies completion/summary back to chat, optionally with diff.

2. Desktop integration: while ChatBot is running, desktop and agent keep the same session; you can "send" a response directly into the chat of the bot with a button Send to user (like the WeChat connector).

Why

• This is the feat: compact and other improvements #1 gap vs OpenClaw/Hermes for non-tech users / mobile — you don't need to be at the machine.
• OpenCode has all the pieces: serve API, permissions, sessions — just no official chat ingress.
• It would also let OpenCode desktop be controlled remotely.

Design proposal

• New subcommand opencode bot with connectors: telegram (official Bot API, minimal), plus a generic HTTP hook mode that any bridge (WeChat/QQ/WhatsApp) can POST to.
• Session isolation: each chat user → separate session (reuses session.manage semantics).
• Replies: text summary + up to N files (small), + link to share URL.
• Security: same permission prompts (chat approval via a second channel) or --auto flag documented as risky.

Related

• [FEATURE]: First-class managed connectors (Google Calendar, Gmail, Slack, Notion, Sheets) with built-in OAuth #38095 (managed connectors OAuth) — that's outbound data access (read Google/Notion). This is inbound control: chat → run opencode.
• ACP (ACP mode returns empty response when used with WeClaw #31717 WeClaw) — 3rd party bridges exist; an official bot gateway would give a blessed path.