Skip to content

docs(readme): lead with multi-channel driving (browser + WeChat + Telegram)#56

Merged
Germey merged 1 commit into
mainfrom
docs/multi-channel-readme
Jul 4, 2026
Merged

docs(readme): lead with multi-channel driving (browser + WeChat + Telegram)#56
Germey merged 1 commit into
mainfrom
docs/multi-channel-readme

Conversation

@acedatacloud-dev

Copy link
Copy Markdown
Member

What & why

README 之前只宣传了 browser/Nexior 一种驱动方式。现在顶部介绍体现「同一个 daemon,多种驱动入口」——浏览器/手机 + 你已经在用的微信 / Telegram 聊天账号,方便客户直接照着 setup。

  • Tagline 更新:点明可从 Nexior、手机、或 WeChat / Telegram 驱动。
  • 架构图后新增 "Two ways to drive it" 段落:① 浏览器/手机(coding-bridge up);② 聊天账号(coding-bridge channels start,一条消息 = 一次 Claude/Codex turn),链接到已有的 Chat channels setup 小节。
  • "Why" 段落同步措辞(browser / phone / WeChat / Telegram)。

纯文档改动,不碰代码。两条链路已在本地对真实的微信 gateway 和真实 Telegram bot 跑通:channels doctor 两个渠道全绿,channels start 两条 outcome=ok turn(Telegram reply 379 chars / WeChat reply 67 chars)。

🤖 对抗评审

纯 README 文案改动(trivial)。自查:锚点 #chat-channels-wechat--telegram 与现有 ## Chat channels (WeChat & Telegram) 标题的 GitHub slug 匹配;coding-bridge up / coding-bridge channels start 命令正确;studio.acedata.cloudcoding-bridge.acedata.cloud 链接有效;无事实错误。VERDICT: CLEAN

…egram)

The intro only advertised the browser/Nexior path. The tagline + a new 'Two ways to drive it' block now make clear the same daemon is also driven from a WeChat or Telegram chat (each message = one Claude Code/Codex turn), linking to the existing Chat channels setup section.
@Germey Germey merged commit 63d67f8 into main Jul 4, 2026
3 checks passed
@Germey Germey deleted the docs/multi-channel-readme branch July 4, 2026 04:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants