安装与配置教程
v1.0.1 · 三种安装方式 + 火山方舟 BYOK 三步开通。遇到问题发邮件 crosschat.app@gmail.com。
方式一:Chrome Web Store(推荐,可自动更新)
需要 Chrome 110+ 且网络能访问 Chrome Web Store。
- 打开商店页:CrossChat — AI 客服回复助手,点击「添加至 Chrome」。
- 安装后自动打开首启引导页:先看 30 秒离线演示,再按需添加客服站点。
- 商店版后续自动更新,无需手动操作。
方式二:Microsoft Edge
Edge 加载项(Add-ons)商店版本正在提交审核,上架后会在此页更新链接。在此之前有两个临时办法:
- 在
edge://settings/system 打开「允许来自其他应用商店的扩展」,然后按方式一从 Chrome Web Store 安装(仍需网络能访问商店);或
- 直接使用方式三的开发者模式加载,Edge 同样支持。
方式三:离线安装(访问不了商店时,开发者模式加载已解压扩展)
说明:Chrome 已禁止直接拖入 .crx 安装第三方扩展,离线安装统一使用「加载已解压的扩展程序」。此方式不经过商店,不会自动更新,新版本需手动替换文件(同一文件夹覆盖可保留配置与数据)。
- 获取安装包(任选其一):
· GitHub 仓库主页 github.com/shizhi3620/crosschat → 绿色「Code」按钮 →「Download ZIP」;
· 或直接下载:crosschat-main.zip。
打包所需文件(含预编译的注入脚本)都已在仓库内,无需安装 Node、无需自行构建。
- 把 ZIP 解压到一个固定目录(之后不要删除或移动,否则扩展会失效),解压后应能看到
manifest.json 与 src/ 文件夹。
- 浏览器地址栏打开
chrome://extensions(Edge 为 edge://extensions),打开右上角「开发者模式」。
- 点「加载已解压的扩展程序」,选择包含
manifest.json 的那个文件夹。
- 出现跨海聊图标即安装成功;浏览器顶部「开发者模式扩展」提示是 Chrome 的正常安全提示。
如果 github.com 也无法访问:可以换网络时点按上面的 ZIP 链接预先下载,或发邮件到 crosschat.app@gmail.com 索取离线包;国内镜像下载点正在准备中。
配置你自己的火山方舟 Key(BYOK,三步)
没有 Key 也能先用离线演示;需要真实 AI 草拟时再做下面三步。Key 只保存在你本机的 chrome.storage.local,请求从浏览器直连火山方舟北京节点,不经过扩展作者的服务器。
- 注册并实名:打开火山方舟控制台 console.volcengine.com/ark,注册火山引擎账号并完成实名认证(个人实名即可)。
- 开通模型:在「在线推理」里开通要用的模型。默认配置是轻量模型
doubao-seed-2-0-mini(翻译、常规回复,便宜)+ 旗舰模型 doubao-seed-2-1-pro(只有纠纷/差评等难单才调用),把模型或接入点 ID 分别复制到设置页的 L1、L2 输入框。
- 创建并测试 Key:在控制台「API Key 管理」创建一个 Key,粘进扩展设置页的 API Key 框,点「测试连接(不保存,即填即测)」。通过后再点页面底部「保存全部设置」正式生效;测试失败不会改动你已保存的配置。
费用:按你自己的火山引擎账户后付费,用多少算多少,扩展不收钱。按内置成本模型(2026-10-15 官方单价口径)估算,典型客服会话每处理 1,000 条约 ¥3.7~¥73.5,常规混合(约六成缓存命中)约 ¥17.7,实际以
方舟价目表与你的账单为准。
测试连接报错怎么看?
- 401:API Key 无效或填错。重新到「API Key 管理」复制完整 Key;注意要的是方舟 API Key,不是火山引擎主账号的 AccessKey。
- 403:账号未实名、账户欠费/余额不足,或该 Key 没有所选模型的调用权限。
- 404:Base URL 或模型 ID 不一致。默认 Base URL 为
https://ark.cn-beijing.volces.com/api/v3,模型 ID 必须与「在线推理」里已开通的完全一致。
- 429:触发限流或免费额度用尽,稍后再试或查看方舟配额。
- 超时 / 连不上:检查网络与代理——北京节点国内一般直连即可,挂海外代理反而可能失败;公司网络请放行
ark.cn-beijing.volces.com。
安装后 30 秒上手
- 首启引导页点「打开演示页面」,在模拟收件箱里跑通:捕获买家消息 → 翻译 / 草拟 → 合规与 PII 检查 → 采纳。
- 在「管理我的客服站点」里添加你实际使用的卖家后台 / CRM / 邮箱域名并授权——不授权的站点完全不注入。
- 打开真实客服页面,选中买家消息,点工具栏的跨海聊图标开始。任何时候扩展都只填草稿,平台发送按钮由你亲自点击。
演示模式下的占位译文/草稿会红底提示「切勿外发」且无法采纳,配置真实 Key 后才会产生可填入发送框的内容。
更多问题见 常见问题 FAQ;数据怎么处理见 隐私政策。
Install & setup guide
v1.0.1 · Three install paths plus a three-step Volcengine Ark BYOK setup. Stuck? Email crosschat.app@gmail.com.
Option 1: Chrome Web Store (recommended, auto-updates)
Requires Chrome 110+ and a network that can reach the Chrome Web Store.
- Open the CrossChat store listing and click “Add to Chrome”.
- The first-run page opens automatically: try the 30-second offline demo, then add customer-service sites as needed.
- Store installs update automatically.
Option 2: Microsoft Edge
The Edge Add-ons submission is under review; this page will link it once published. Meanwhile you can either enable “Allow extensions from other stores” at edge://settings/system and install from the Chrome Web Store (store must still be reachable), or use Option 3, which works in Edge as well.
Option 3: Offline install (unpacked extension in developer mode)
Chrome no longer allows side-loading .crx files, so offline installs use “Load unpacked”. This path does not auto-update; replace the folder contents manually for new versions (overwriting the same folder keeps your settings).
- Get the package: on github.com/shizhi3620/crosschat use the green “Code” button → “Download ZIP”, or download crosschat-main.zip directly. Everything needed to load it (including the prebuilt injected script) is in the repo — no Node install or build step required.
- Unzip into a permanent folder (do not delete or move it afterwards); you should see
manifest.json and a src/ folder inside.
- Open
chrome://extensions (edge://extensions in Edge) and enable “Developer mode” (top-right).
- Click “Load unpacked” and select the folder containing
manifest.json.
- The CrossChat icon appears. The “developer-mode extensions” browser warning is a normal Chrome safety notice.
Bring your own Volcengine Ark key (three steps)
The offline demo works without a key; configure BYOK only when you want real AI drafts. The key is stored solely in your local chrome.storage.local; requests go browser-to-Ark (Beijing) through no server of ours.
- Register and complete identity verification at the Ark console: console.volcengine.com/ark.
- Enable the models under “Online inference”: defaults are the lightweight
doubao-seed-2-0-mini (L1: translation and routine replies) and doubao-seed-2-1-pro (L2: disputes and strongly negative messages only). Copy the model/endpoint IDs into the L1 and L2 fields.
- Create an API key under “API Key management”, paste it into the options page, and click “Test connection” — it tests the form values without saving and never overwrites your saved setup on failure. Save only after the test passes.
Cost: post-paid on your own Volcengine account; the extension charges nothing. At the built-in cost model (2026-10-15 official prices), typical support traffic is roughly ¥3.7–¥73.5 per 1,000 conversations depending on mix (≈¥17.7 at ~60% cache hits). The
Ark price list and your bill are authoritative.
Test-connection errors
- 401: invalid or mistyped API key. Recopy it from “API Key management” — it is an Ark API key, not your main Volcengine AccessKey.
- 403: identity verification incomplete, insufficient balance, or the key lacks access to the selected model.
- 404: Base URL/model ID mismatch. The default Base URL is
https://ark.cn-beijing.volces.com/api/v3; the model ID must exactly match one enabled in “Online inference”.
- 429: rate limit or quota exhausted — retry later or check Ark quota.
- Timeout / network: check network and proxies (the Beijing endpoint is usually direct in mainland China; overseas proxies may break it) and allow
ark.cn-beijing.volces.com through corporate firewalls.
First 30 seconds
- Open the demo from the first-run page and walk through capture → translate/draft → compliance & PII checks → adopt.
- Add and authorize the seller-backend / CRM / webmail domains you actually use — nothing is injected on sites you don’t grant.
- On a real support page, select a buyer message and click the toolbar icon. The extension only ever fills a draft; you click the platform’s send button.
Demo placeholders are shown with a red “do not send” warning and cannot be adopted into a reply box; adoptable content appears only after a real key is configured.
More answers in the FAQ; data handling is described in the Privacy Policy.