20:"$Sreact.view_transition" 21:I[9754,["/_next/static/chunks/2t36f5p4pjzlb.js","/_next/static/chunks/1gyqeidjm5eoa.js","/_next/static/chunks/0_fjnxc4tt_l_.js","/_next/static/chunks/1ymt1shyhmu-4.js","/_next/static/chunks/3kv2zf0i7s2wc.js","/_next/static/chunks/1vs_3g_g75zmk.js","/_next/static/chunks/2g4dh802s8oz3.js","/_next/static/chunks/1bc3f0shukf1j.js","/_next/static/chunks/192kgs9v_t14j.js","/_next/static/chunks/0z6pw0v5c_lx5.js","/_next/static/chunks/08r60e6icmtkc.js","/_next/static/chunks/3trx6c0i7_x-3.js","/_next/static/chunks/40sro5bzp9bi_.js","/_next/static/chunks/1wgf3tk38y6cf.js"],"ProjectDetail"] 22:T453c, 在场网络 · astrbot_plugin_hapi_connector

astrbot_plugin_hapi_connector

一次在场，多处并行

一条聊天指令，同时抵达 QQ、微信、Telegram，再汇入 HAPI 中枢，统一调度多个 AI 编码会话。人留在原地，代码在别处继续。

vibe coding 随时随地作者 lijinhao999 语言 Python 协议 AGPL-3.0

01在场射线 · the platform ray

从一条聊天，分路到你常用的三个平台

这条插件让你不必守在电脑前：QQ、微信、Telegram 哪一个顺手，就在哪一条线上继续。你在手机上敲下的每一条指令，都以 /hapi 开头，从聊天里发射出去。

三条分路共用同一个中心，就像同一次话语被同时送达多处终端——你是原点，平台是射线，而不是一个需要打开的网页。

QQ桌面 · 移动

微信 · WeChat经平台对话接入

Telegram云端会话接入

02中枢脊梁 · the HAPI spine

一条脊梁，托住所有会话

HAPI 后端本地统一中枢

多代理调度一个中枢、多路并发

会话管理启动 · 切换 · 恢复

所有三路消息在 HAPI 枢纽汇合。它是一个管理多个 AI 编码代理会话的后端，统一规划思路、派发任务，而不是每个平台各自为政。

中枢扮演“接线员”：把本地的一次调度，翻译成对远端代理的并发请求，再带回结果供你分路查看。

03会话驾驶 · the session pilot

多路代理，由你来判向

从枢纽发散出去的，是 Claude Code、Codex、Cursor 等代理节点，以及 Grok、Kimi、OpenCode、Pi 更多选择。你可以在会话之间发送消息、切换模型、传输文件。

每个代理都是一段独立的轨道：/hapi 指令负责调度，聊天窗口各自隔离，不会互相串话。

pilot · send发送消息把指令或上下文灌进被选的会话

pilot · switch切换代理在编码助手之间无缝转向

pilot · file传输文件把产出带回你当前的聊天

04审批检查点 · the approval checkpoint

改变到站前，先过你这一关

远程不等于失控。仅管理员可用 的 /hapi 指令保留在权限检查点，执行触达远端前由你点头。剪眼陌生会话、放行关键步骤，都由这一道入口把关。

这不是一个模拟审批框，而是真实的权限路由：谁被允许调度代理、哪一步需要放行，都写在这条脊梁的这条支路上。

✓ 指令仅 管理员 可用

05只在本地 · the local-only privacy

数据留在原地，不外传

整条在场网络的会话数据全部留在本地。中枢在你自己的机器上运行，平台只是运输的通道，内容本身不落入私有云端。

你在外出时推进编码，回来时仍能在这条本地脊梁上接续，不需要为一个远程服务上传。

✓ 需要先部署 HAPI 后端（本地运行）

06从任何一端开始 · start anywhere

在你想待的地方，
接上想编码的键盘。

部署一个 AstrBot 插件，把手机上的聊天变成远端 AI 会话的调度台。今天从一条 /hapi 指令开始。

仓库 astrbot_plugin_hapi_connector Stars 194 Forks 18 协议 AGPL-3.0

在 GitHub 查看仓库 ↗

astrbot_plugin_hapi_connector · 通过聊天远程控制 AI 编码会话 · vibe coding anywhere

23:T440a, Telepresence Network · astrbot_plugin_hapi_connector

astrbot_plugin_hapi_connector

One presence,many places at once

A single chat command travels out to QQ, WeChat and Telegram, folds back into the HAPI hub, and fans out to a set of AI coding sessions. You stay put; the code keeps moving.

vibe coding from anywhere by lijinhao999 Python AGPL-3.0

01the platform ray

A single thread,split across the chat apps you already use

The plugin frees coding from a desk. Reach it through QQ, WeChat or Telegram — whichever line is in your hand. Every command you type rides out of a chat bubble, always opening with /hapi.

All three rays share one center. It is the same voice heard in several places at once — you are the origin, the platforms are the spokes, and there is no separate page to open.

QQDesktop · Mobile

WeChatVia chat thread

TelegramThrough session

02the HAPI spine

One spine,carrying every session

HAPI backendlocal hub

Multi-agent dispatchone hub, many lines

Session controlstart · switch · resume

All three routes fold into the HAPI hub, a backend that manages several AI coding agent sessions. It plans, routes and dispatches work in one place instead of leaving each platform to figure it out alone.

The hub plays switchboard: it turns a single local request into concurrent calls to distant agents, then brings the results back for you to follow along any of the lines.

03the session pilot

Parallel agents,steered by you

Spokes out of the hub reach Claude Code, Codex and Cursor — with Grok, Kimi, OpenCode and Pi alongside. From one chat you can send messages to a session, switch between models, and move files in and out.

Each agent runs as its own isolated track. /hapi drives the dispatch while the chats stay separate, so work never leaks between lines.

pilot · sendSend messagespush context and prompts into the chosen session

pilot · switchSwitch agentsturn between coding assistants seamlessly

pilot · fileMove filesbring the output back into your current chat

04the approval checkpoint

Before a change lands,it passes through you

Remote does not mean unchecked. The /hapi commands are admin-only, held at a permission checkpoint where you decide before anything reaches the agents. Cross-check an unfamiliar session, approve a critical step — gate it right here.

This is not a mock approval widget; it is a real permission route written into this branch of the spine, deciding who may dispatch an agent and which step needs your sign-off.

✓ Commands are admin-only

05the local-only privacy

Data stays put,on your side

Session data across the whole telepresence network stays entirely local. The hub runs on your own machine — the chat platforms are just the delivery lanes, and the content itself never lands in someone else's cloud.

Step out and keep coding, then pick the thread back up on this local spine. Nothing needs to be uploaded to a remote service along the way.

✓ You first deploy the HAPI backend (runs locally)

06start anywhere

Stay wherever you like,
and reach the keyboard you want to type on.

Deploy an AstrBot plugin and turn the chat in your pocket into a control deck for remote AI sessions. It starts with a single /hapi command.

Repo astrbot_plugin_hapi_connector Stars 194 Forks 18 License AGPL-3.0

View the repository on GitHub ↗

astrbot_plugin_hapi_connector · remote AI coding sessions from your chat apps · vibe coding anywhere

a:[["$","$20",null,{"enter":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-enter","default":"none"},"exit":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-exit","default":"none"},"update":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-update","default":"none"},"default":"none","children":["$","$L21","cmt2zh10b00xe6271i4s14w42:zh-CN:beautified",{"project":{"id":"cmt2zh10b00xe6271i4s14w42","slug":"lijinhao999-astrbot-plugin-hapi-connector","name":"astrbot_plugin_hapi_connector","description":"通过聊天远程控制 AI 编码会话的 AstrBot 插件","authorName":"lijinhao999","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"data_ai_tools","experienceUrl":null,"qualityScore":32,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zh10u00xq6271nkcm0ppz","kind":"artifact","artifact":{"schemaVersion":"localized-static-html-v4","kind":"static_html","locales":["zh-CN","en"],"defaultLocale":"zh-CN","documents":{"zh-CN":"$22","en":"$23"},"designDirections":{"schemaVersion":"dodot-design-directions-v1","directions":[{"id":"direction-remote-trigger","name":"遥控扳机 / Remote Trigger","projectMetaphor":"把一条聊天指令当成按下的远程扳机：一条 /hapi 指令从手机上的聊天气泡出发，隔空扣动一台远端的 AI 编码会话。编码不再需要在电脑前发生，而是“隔着聊天框扣一下扳机,代码就在别处继续”。","signatureVisual":"一个被渲染成巨大可按下按钮的 /hapi 命令行，按下后派生出若干段带信号振铃色的“脉冲弧线”射向代表各类代理的独立会话节点。核心是非截图式的“扳机图”：一条指令与远处的一个会话点亮关系。","heroGeometry":"几何为左右对峙：左侧一块凸起的“扳机按钮”（粗描边的指令文本 + 环形按压反馈），右侧一条从触发器水平射入的弧线脉冲，击中一个独立的暗色会话圆点；背景留白,只用一处受控的信号色。","sectionSequence":["the-pull-the-trigger","the-single-command","where-it-reaches","the-chat-isolation","the-approval-gate","the-local-boundary"],"surfaceModel":"纸感按压表面：每个章节像一张可被“按下”的卡片，焦点/悬停时有明确的按压位移与被按铃的高对比指令文字；层级靠 z 位移而非阴影堆叠,连续章节之间用不同的按压深度区分节奏。","palette":"近黑墨底为主,指令与扳机用单一高饱和橙红(#FF4D2E)作为“按下”信号在整页只出现几次;会话节点用冷灰蓝;背书用深绿。颜色是“扳机按下”的语义,不做渐变光晕。","typography":"等宽字体承担所有指令与命令,衬线/黑体承担叙述标题;标题用大字号、左对齐、紧排,形成“机器与叙述”的双声部。","desktopComposition":"桌面为纵向“扣动序列”：首屏横向扳机对峙作 Hero,随后每节以卡片错位(左->右->左)呈现按压与命令;左右分栏在叙述区之间穿插一条横向脉冲轨迹线贯穿全页。","mobileTransformation":"390px 下扳机对峙改为上下堆叠,按压环形缩小为拇指标尺;横向脉冲轨迹线改为纵向信号链,用户可沿链逐节下滑“依次扣动”;卡片按压同概念,但位移量压缩为垂直方向。","mediaStrategy":"无本地素材,移除媒体区;以证据驱动的指令文本、会话节点与脉冲关系线作为全部视觉,不伪造产品截图。","forbiddenPatterns":["不得使用浏览器/终端/手机/编辑器外壳","不得用三卡指标堆砌首屏","不得用发光网格或粒子替代关系线","不得伪造聊天记录、审批弹窗或仪表盘截图"],"compositionFingerprint":"button-command-dashboardless: 单个可点击的大号 /hapi 指令 + 派生脉冲弧线 + 错位按压卡片节奏"},{"id":"direction-telepresence-hub","name":"分身在场 / Telepresence Hub","projectMetaphor":"一次在场,多处并行:开发者只点一次,消息同时到达 QQ、微信、Telegram,再汇入 HAPI 中枢统一调度多个代理会话。像一个“分身在场”的网络,一个大脑分居多具终端。","signatureVisual":"中心原点(user/你)向外辐射到 QQ/微信/Telegram 三个平台环,再从平台环向内汇入 HAPI 中枢,中枢再分发到 Claude/Codex/Cursor 等节点;整体是一张非截图的“在场的放射网络”。","heroGeometry":"几何为中心辐射:中心一个实心原点(你),向外分岔 3 条折线到达三个平台标签,然后三条线拐弯汇入一个底部枢纽圆环(HAPI),枢纽再向外发散到多个代理节点。用连线关系而非界面外壳表达。","sectionSequence":["present-everywhere-at-once","the-platform-ray","the-hapi-spine","the-session-pilot","the-approval-checkpoint","the-local-only-privacy","start-anywhere"],"surfaceModel":"网络布线表面：整页是一张可沿直线/折线滑动的“在场网络”,平台与代理以节点呈现,连线会根据滚动逐步点亮;表面没有卡片墙,而是节点、折线、枢纽环与细线连接的整体拓扑。","palette":"浅色纸底为主,枢纽与“你”的中心用墨黑实心,三条平台线各取一条低饱和分割色(QQ 蓝/微信绿/Telegram 青),代理节点用灰;颜色承担“分路”的语义而非装饰。","typography":"中枢与代理统一用同一套窄标题,平台标签与节点用等宽小字轴标;标题采用窄幅、右对齐、居中于节点行,形成“路线图/地图”的注记感。","desktopComposition":"桌面为一张不断下滚的“在场地图”：首屏整幅放射网络作 Hero,随后逐层切到平台分路、HAPI 脊柱、会话节点;左右采用非对称副栏承载节点注记,整体像在看一张动态路由图。","mobileTransformation":"390px 下放射网不再是整幅缩小的地图,而是改为“逐段折叠路由”:每次滚动只展开一段“你->平台”或“平台->HAPI”的折线,用户像逐车站经过;节点从横排改为纵向序列,连线变成逐段的引线。","mediaStrategy":"无本地素材,移除媒体区;以平台名、代理名与枢纽连线的拓扑关系作为全部视觉,不伪造任何界面截图。","forbiddenPatterns":["不得把首屏做成终端/浏览器/编辑器外壳","不得用三卡指标层作为主体视觉","不得堆叠发光圆点粒子来冒充网络","不得伪造会话订阅列表、审批弹窗或控制面板"],"compositionFingerprint":"hub-spoke-topology no-shell: 中心原点 + 平台分路折线 + HAPI 枢纽 + 代理节点,整页为可滚动点亮的分段路由拓扑"},{"id":"direction-signal-telephone","name":"长途接线 / Signal Line","projectMetaphor":"把一次远程编码想象成一条贯穿的长途信号线:声音从手机聊天口进入,经过 HAPI 中继,再到远端代理落笔。风格是把“vibe coding anywhere”转译为一段有起点的信号旅程。","signatureVisual":"一条沿页面纵向蜿蜒的连续信号主线:起点是“你说话的聊天口”,途经一个中继继电器(HAPI),到达“落笔的代理”;主线本身是可读、可滚动的叙事载体。","heroGeometry":"几何为纵向蜿蜒线:S 形主线从左上聊天口出发,穿过画面中段的中继节点,在右下抵达代理;主线上挂着小型的“语音波形/会话刻度”,表示信号在流动。","sectionSequence":["speak-anywhere","the-line-to-hapi","the-relay","the-planning-session","the-file-return","the-wheel-turns-locally"],"surfaceModel":"单线引导表面：整页一条主轴贯穿,内容挂在信号线与站点刻度上,章节之间靠信号线本身的转向与站点停顿切换;没有横向卡片带,空间由线主导,站点与章节用同一条线串联。","palette":"近似双色硬对撞:深靛墨底配橙黄信号色(#F5B828)作主线与站点,辅助文字用冷灰;整页仅有“线”与“站点”两套颜色,强调信号流动而非装饰。","typography":"标题用极窄的粗黑体、沿主线站点右排,正文为小号灰衬线;站点标题用大写的等宽提示词(如 GO / RELAY / LAND)形成“铁路站牌”节奏。","desktopComposition":"桌面为纵向信号旅程:首屏展示完整蜿蜒主线一瞥,随后按站逐段放大主线局部,章节标题作为“站牌”锚在转弯处;引入区与细节交替出现,像沿一条线旅行的进度。","mobileTransformation":"390px 下蜿蜒主线不再缩成全程,而是改为“逐站一行线性推进”:每一站只展示主线的下一段折线,用户向上滑动即从上一站走到下一站,行程感完全由进度决定;站点刻度纵向排布。","mediaStrategy":"无本地素材,移除媒体区;以信号主线、中继节点与站点刻度作为全部视觉,不伪造任何截图或模拟界面。","forbiddenPatterns":["不得用终端/编辑器/浏览器/手机外壳承接主体","不得以三卡指标填充首屏","不得用闪烁粒子替代信号主线","不得伪造消息气泡、审批界面或文件列表截图"],"compositionFingerprint":"single-journey-signal-line: 一条纵向蜿蜒主线 + 中继 + 模拟会话站点,整页为可算序号的滚动旅程"}],"selectedDirectionId":"direction-telepresence-hub","selectionRationale":"这是三个方向中最贴近项目真实机制的一个。项目证据(build_software / automate_work / operate 意图,以及“连接hapi,随时随地vibe coding”、“支持 QQ/微信/Telegram 平台、Claude Code/Codex/Cursor 等代理”、“数据全部留在本地”)本身就构成一张多对多的在场网络:单一用户通过多个聊天平台抵达 HAPI 中枢,再由中枢管理多个编码代理会话。hub-spoke 拓扑不需要伪造产品截图,就能诚实表达「一次在场、多处并行」的运作关系,且能覆盖审批检查点与本地隐私两个证据点。相比 direction-remote-trigger 的「按钮+弧线」(更偏隐喻、偏离多平台结构)和 direction-signal-telephone 的「单线旅程」(只强调一条单一链路、弱化了多代理并行),telepresence hub 的放射网络能同时容纳多平台与多代理两个核心分支,信息密度最高、最忠于证据,且其 surfaceModel(可滚动点亮的布线网络)和 mobile 重构(逐段折叠路由)都与另外两个方向在隐喻、标志视觉、Hero 几何、章节顺序、表面模型和手机重构上实在不同。"},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"direction-telepresence-hub","projectMetaphor":"一次在场,多处并行:开发者只点一次,消息同时到达 QQ、微信、Telegram,再汇入 HAPI 中枢统一调度多个代理会话。像一个“分身在场”的网络,一个大脑分居多具终端。","signatureVisual":"中心原点(user/你)向外辐射到 QQ/微信/Telegram 三个平台环,再从平台环向内汇入 HAPI 中枢,中枢再分发到 Claude/Codex/Cursor 等节点;整体是一张非截图的“在场的放射网络”。","compositionFingerprint":"hub-spoke-topology no-shell: 中心原点 + 平台分路折线 + HAPI 枢纽 + 代理节点,整页为可滚动点亮的分段路由拓扑","heroGeometry":"几何为中心辐射:中心一个实心原点(你),向外分岔 3 条折线到达三个平台标签,然后三条线拐弯汇入一个底部枢纽圆环(HAPI),枢纽再向外发散到多个代理节点。用连线关系而非界面外壳表达。","sectionSequence":["present-everywhere-at-once","the-platform-ray","the-hapi-spine","the-session-pilot","the-approval-checkpoint","the-local-only-privacy","start-anywhere"],"surfaceModel":"网络布线表面：整页是一张可沿直线/折线滑动的“在场网络”,平台与代理以节点呈现,连线会根据滚动逐步点亮;表面没有卡片墙,而是节点、折线、枢纽环与细线连接的整体拓扑。","palette":"浅色纸底为主,枢纽与“你”的中心用墨黑实心,三条平台线各取一条低饱和分割色(QQ 蓝/微信绿/Telegram 青),代理节点用灰;颜色承担“分路”的语义而非装饰。","typography":"中枢与代理统一用同一套窄标题,平台标签与节点用等宽小字轴标;标题采用窄幅、右对齐、居中于节点行,形成“路线图/地图”的注记感。","desktopComposition":"桌面为一张不断下滚的“在场地图”：首屏整幅放射网络作 Hero,随后逐层切到平台分路、HAPI 脊柱、会话节点;左右采用非对称副栏承载节点注记,整体像在看一张动态路由图。","mobileTransformation":"390px 下放射网不再是整幅缩小的地图,而是改为“逐段折叠路由”:每次滚动只展开一段“你->平台”或“平台->HAPI”的折线,用户像逐车站经过;节点从横排改为纵向序列,连线变成逐段的引线。","mediaStrategy":"无本地素材,移除媒体区;以平台名、代理名与枢纽连线的拓扑关系作为全部视觉,不伪造任何界面截图。","evidencePlan":["中心原点至 QQ/微信/Telegram 三条折线,逐一对应 evidence: 支持平台 Like QQ, WeChat, Telegram(en) 与通过聊天远程管理(en)","HAPI 枢纽环对应 evidence: 连接 HAPI 后端,统一管理多个 AI 编码代理会话(zh-CN)","从枢纽发散到 Claude Code/Codex/Cursor 等节点对应 evidence: 支持 AI 编码助手,如 Claude Code、Codex、Cursor、Grok、Kimi(I should use the en localization list『Claude Code, Codex, and Cursor』which matches overview)","approval-checkpoint 章节对应 evidence: 支持审批权限与 /hapi 仅管理员可用","local-only-privacy 章节对应 evidence: 数据全部留在本地","Web 管理面板与文件传输以注记形式在节点副栏出现,不伪造截图"],"localeContract":{"zh-CN":"通过聊天远程控制 AI 编码会话的 AstrBot 插件,连接 HAPI 后端,支持 Claude Code、Codex、Cursor 等代理,可发送消息、审批权限、切换模型、传输文件,并提供 Web 管理面板;数据本地存储,适合外出时继续推进编码任务。","en":"AstrBot plugin that lets you remotely manage AI coding sessions through chat platforms like QQ, WeChat, and Telegram. It connects to the HAPI backend, supports agents like Claude Code, Codex, and Cursor, and keeps all data local."},"forbiddenPatterns":["不得把首屏做成终端/浏览器/编辑器外壳,或任何假界面壳","不得用三卡指标层作为主体视觉","不得堆叠发光圆点/网格/粒子来冒充网络拓扑","不得伪造聊天记录、会话订阅列表、审批弹窗或控制面板截图","不得在不具备本地素材时加载远程运行时图片或建立占位媒体框"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"页面忠实实现 direction-telepresence-hub 的 brief：首屏为中心辐射在场网络（你的原点 -> QQ/微信/Telegram 三平台折线 -> HAPI 枢纽环 -> Claude Code/Codex/Cursor 等代理节点），全页无界面外壳、无伪造截图，节点+折线+枢纽环的布线表面而非卡片墙。sectionSequence 与证据逐一对应，双语章节结构等价且自然，手机端布局折叠为纵向重构。存在个别中文字词小瑕疵，但均不阻断设计契约。","checks":{"projectFit":{"passed":true,"evidence":"选中方向 direction-telepresence-hub 的 hub-spoke 拓扑精确落地：hero 的 SVG（zh line 196-234 / en line 189-223）实现了「中心原点 you -> 三条 platform 折线(qq/wechat/telegram) -> 底部 HAPI 枢纽圆环 -> 四路 agent 节点(Claude Code/Codex/Cursor 及 Grok/Kimi/OpenCode/Pi)」；section 顺序（the-platform-ray、the-hapi-spine、the-session-pilot、the-approval-checkpoint、the-local-only-privacy、start-anywhere）与 brief sectionSequence 一致，首屏 hero 承担 present-everywhere-at-once。"},"evidenceBound":{"passed":true,"evidence":"平台射线对应 evidence「支持 QQ/微信/Telegram」；HAPI 枢纽对应「连接 HAPI 后端、统一管理多个 AI 编码代理会话」；agent 节点对应「支持 Claude Code、Codex、Cursor、Grok、Kimi、OpenCode、Pi」；approval 章节对应「/hapi 仅管理员可用、审批权限」；local-only 章节对应「数据全部留在本地」；stars 194 / forks 18 / AGPL-3.0 / Python 均与 material 中的 repository 事实一致，无无依据声明。"},"signatureVisual":{"passed":true,"evidence":"signatureVisual 真实存在于两版 HTML hero 的内嵌 SVG：中心实心原点 + 三色平台折线 + 墨黑 HAPI 枢纽圆环 + 灰色代理节点，且 scroll-driven 动画（animation-timeline:view()）实现连线随滚动逐步点亮，匹配 brief「可滚动点亮的布线网络」。"},"mobileTransformation":{"passed":true,"evidence":"两版 CSS 均在 max-width:820px 将 .hero-grid 与 .grid2 折叠为单列、.cardshape 变为单行，net 收窄至 560px，节点/副栏呈纵向序列，实现 brief 的「逐段折叠路由 / 节点纵向化」；qa-report 中 zh-CN 与 en 的 scrollHeight 在桌面(3526/3767)与移动(4727/5203)差异明显，证明发生真实布局重构而非等比缩放。"},"localeParity":{"passed":true,"evidence":"zh-CN 与 en 两版结构、章节编号、节点/卡/链接完全对齐；英文文案（如 A single thread, split across the chat apps you already use / Data stays put）读起来自然、非逐字直译，符合 localeContract 与 localizations；网页 lang=zh-CN / en 正确。"},"antiTemplate":{"passed":true,"evidence":"compositionFingerprint「hub-spoke-topology no-shell」成立：首屏不是终端/浏览器/编辑器外壳，无三卡指标层作为首屏主体，无发光网格/粒子冒充网络，第三节的 cardshape 是无数字的边框顶描述卡（send/switch/file 的操作注记），属 brief 允许的注记而非指标堆砌，其余表面由 node-list 与折线拓扑主导。"},"noFakeUi":{"passed":true,"evidence":"两版 HTML 均无 /

从一条聊天，分路到你常用的三个平台

一条脊梁，托住所有会话

多路代理，由你来判向

改变到站前，先过你这一关

数据留在原地，不外传

在你想待的地方，接上想编码的键盘。

A single thread,split across the chat apps you already use

One spine,carrying every session

Parallel agents,steered by you

Before a change lands,it passes through you

Data stays put,on your side

Stay wherever you like,and reach the keyboard you want to type on.

在你想待的地方，
接上想编码的键盘。

Stay wherever you like,
and reach the keyboard you want to type on.