dsh-shengwang-voice-bridge
从 Shengwang Conversational AI 到 DeepSeek Harness 的回环式 OpenAI 兼容流式桥接
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:chenjie1129/deepseek-harness-shengwang-voice-bridge#65a84fcfafb59852ce43a303842ed9181057d6b0Shengwang Voice Bridge 以 dsh-shengwang-voice-bridge 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
An isolated DeepSeek Harness plugin with a bilingual configuration page, browser microphone controls, and the streamed OpenAI Chat Completions endpoint required by Shengwang (Agora) Conversational AI.
Harness Settings → Plugins → Voice
↕ browser microphone and call controls
Shengwang RTC → managed ASR → Conversational AI → managed TTS
↓ HTTPS OpenAI SSE
Public path-restricted tunnel → 127.0.0.1:54120
↓
This plugin ↔ one private, tool-disabled DeepSeek Harness session
This is an MVP/PoC. It is not an ACP frontend, an audio codec plugin, or a public network server.
The deterministic suite and packed-browser smoke do not prove a live Shengwang account, a live DeepSeek model route, voice quality, or production latency. Those claims require the final microphone call with a credentialed account.
0.1.1-rc.2-compatible packages^22.19.0 or >=24/v1/chat/completionscorepack pnpm install
corepack pnpm test
corepack pnpm run typecheck
npm pack
dsh plugin --profile web add ./dsh-shengwang-voice-bridge-0.2.0.tgz
dsh --profile web
Open Settings → Plugins → Voice:
CN for a shengwang.cn mainland project./v1/chat/completions. It must forward only that path to 127.0.0.1:54120.Advanced deployments can still override port, tokenEnv, appCertificateEnv, provider, model, cwd and request bounds in Cordis config. Normal browser setup does not require editing YAML.
The Start button asks the plugin host to create a Shengwang agent using managed Deepgram STT, this plugin's Custom LLM endpoint, and managed MiniMax TTS. The App Certificate stays on the Harness host; only a one-hour RTC capability reaches browser JavaScript. The browser joins that channel and owns exactly one microphone track until End call, page disposal or a failed start.
Shengwang sends the configured bridge token as Authorization: Bearer .... A client interruption normally closes the LLM stream; the plugin maps that disconnect to agent.cancel({ kind: 'user' }).
The public callback URL is not created by this package. Use a path-restricted relay or tunnel; never expose the Harness Web UI or the bridge control endpoints.
curl --fail http://127.0.0.1:54120/health
curl --no-buffer \
-H "Authorization: Bearer $DSH_SHENGWANG_BRIDGE_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"model":"deepseek-harness","stream":true,"messages":[{"role":"user","content":"Say hello briefly."}]}' \
http://127.0.0.1:54120/v1/chat/completions
| Route | Auth | Purpose |
|---|---|---|
GET /health | No | Listener readiness only |
POST /v1/chat/completions | Bearer | Stream one text turn |
POST /v1/cancel | Bearer | Local cancellation probe |
POST /v1/reset | Bearer | Dispose owned Harness conversation state |
GET /api/shengwang-voice/config | Same origin | Redacted settings and credential status |
PUT /api/shengwang-voice/config | Same origin | Settings plus write-only credential replacement |
POST /api/shengwang-voice/session/start | Same origin | Create Shengwang agent and browser RTC capability |
POST /api/shengwang-voice/session/stop | Same origin | Stop a plugin-owned Shengwang agent |
Only the last user message is admitted because the Harness session already owns conversation history. Images, audio request parts, non-streaming replies and tool/function requests are rejected.
MIT