Skip to content

docs(reference/ecosystem): add Vox AI Relay to alternative clients - #162

Open
Xilebo123 wants to merge 2 commits into
clawdocs:gh-pagesfrom
Xilebo123:vox-ai-relay-client
Open

Xilebo123 wants to merge 2 commits into
clawdocs:gh-pagesfrom
Xilebo123:vox-ai-relay-client

Conversation

@Xilebo123

Copy link
Copy Markdown

Adds Vox AI Relay to ## Alternative clients and frontends on reference/ecosystem, and registers the repository in scripts/ecosystem-repos.json so refresh-stars.mjs picks it up.

Why it fits the section: it is a real Gateway client, not a proxy. app/src/main/java/pl/marcin/openclaw/gateway/GatewayProtocol.kt pins minProtocol and maxProtocol to 4, so it connects to the Gateways that rejected protocol 3 clients since v2026.5.19 — the same reason WebClaw is marked unusable there. Pairing goes through the documented openclaw devices list approval flow. On top of the Gateway it adds on-device speech recognition, sentence-level TTS streaming and mic barge-in that stops generation mid-run; push comes from self-hosted ntfy, so no Firebase project is involved.

Keeping it honest, as the page does for other entries:

  • labelled New project, first release 2026-11-10, v0.8.0 marked as a pre-release with a debug-signed APK;
  • Not tested by clawdocs stated in the entry itself;
  • no claim about which Gateway build was used in production, because I have not run one against v2026.10.4 yet.

Markdown-only insertion plus one line in the repo list, no internal docs links added, so npm run build link checks are unaffected. I did not run the local Docusaurus build — the diff touches only a prose section and the JSON list.

This branch has not been deployed

No deployments
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.

1 participant