beiyege-01/dsh-voice-ai-girlfriend-plugin
Voice AI girlfriend for the Web UI: FunASR mic input, Qwen3-TTS spoken replies, companion animation window, and two-way QQ chat (text/voice/image push) via NapCat.
Listed
0
Voice
Bundle verified
Preview
What it does
Voice AI girlfriend for the Web UI: FunASR mic input, Qwen3-TTS spoken replies, companion animation window, and two-way QQ chat (text/voice/image push) via NapCat.
Best for
- DSH Web users building a voice-driven companion experience with Chinese speech recognition and cloned-voice replies.
- Users who want a companion animation window and bidirectional QQ messaging through NapCat.
Not ideal for
- Standalone plugin installations without the companion voice bridge and its FunASR/Qwen3-TTS setup.
- Users who do not want to operate NapCatQQ or provide their own animation media for the optional QQ and companion-window features.
README
DSH 语音 AI 女友插件(voice-ai-girlfriend)
DeepSeek Harness 的浏览器语音插件:麦克风语音输入、回复朗读(TTS)、AI 女友动画窗、QQ 双向对话。
✅ 已适配 DSH rc.8(当前主线):
dsh.bundlemanifest +conversation.input.dock/left槽位按 rc.8 协议实现;含数字人(DUIX)控制、DeepSeek 余额 badge(stats 行)、五态麦克风。dsh plugin add即可安装。
⚠️ 本插件是完整方案的一部分:语音识别/合成依赖配套的 voice bridge(Python 服务,whisper/FunASR + Qwen3-TTS),QQ 对话依赖 NapCatQQ。请配合完整仓库使用:beiyege-01/dsh-voice-ai-girlfriend(含桥接代码、模型准备、一键启动脚本、安装文档)。
安装
dsh plugin --profile web add github:beiyege-01/dsh-voice-ai-girlfriend-plugin
pnpm ≥10 对 git 依赖的构建脚本有 allowBuilds 限制:按安装时 pnpm 打印的提示,在 profile 的
pnpm-workspace.yaml的allowBuilds里加一行允许esbuild后重跑。
功能
- 🎙️ 语音输入:麦克风 → 桥接 FunASR 中文识别 → 注入对话(连续聆听、自动端点)
- 🔊 语音回复:回复按句子流式 TTS 朗读(Qwen3 声音克隆,音色由参考音频决定)
- ⚡ 插话/排队:亮=说话打断回复;灭=回复读完句子排队接上
- 👧 数字人窗口:右侧动画窗(空闲/说话视频,素材自备)
- 💬 QQ 双向:QQ 消息注入对话 + 回复文本/语音/图片推送(NapCat)
使用前提
- 克隆主仓库并按其 README 装好 voice bridge(
start-all.cmd一键) - 本插件的桥接地址默认
http://127.0.0.1:8765(localStorages2s.voice.bridge可改)
构建
npm install
node build.mjs # 产物 lib/client.js(browser bundle)
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:beiyege-01/dsh-voice-ai-girlfriend-plugin in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.