anomalyco / anomalyco/opencode
[FEATURE] Drive OpenCode from chat apps: official "agent as a bot" gateway (Telegram/Slack/webhook) — the OpenClaw-class gap
@rekram1-node is already working on this.
Since Aug 9, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
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:
-
A background
opencode bot-style runtime (or an official start of the existingserve/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.
-
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 #1 gap vs OpenClaw/Hermes for non-tech users / mobile — you don't need to be at the machine.
- OpenCode has all the pieces:
serveAPI, permissions, sessions — just no official chat ingress. - It would also let OpenCode desktop be controlled remotely.
Design proposal
- New subcommand
opencode botwith 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.managesemantics). - Replies: text summary + up to N files (small), + link to share URL.
- Security: same permission prompts (chat approval via a second channel) or
--autoflag documented as risky.
Related
- #38095 (managed connectors OAuth) — that's outbound data access (read Google/Notion). This is inbound control: chat → run opencode.
- ACP (#31717 WeClaw) — 3rd party bridges exist; an official
botgateway would give a blessed path.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.