docs: mention voice ACP clients with a qwen-audio-agent example - #2690
docs: mention voice ACP clients with a qwen-audio-agent example#2690x-lixu wants to merge 2 commits into
Conversation
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1d0cc2673a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| Then open a new conversation in Zed's Agent panel. See [Using in IDEs](https://moonshotai.github.io/kimi-code/en/guides/ides) for JetBrains setup and troubleshooting, and the [`kimi acp` reference](https://moonshotai.github.io/kimi-code/en/reference/kimi-acp) for the full capability matrix. | ||
|
|
||
| ACP clients are not limited to editors. For example, [qwen-audio-agent](https://github.com/QwenAudio/qwen-audio-agent) is a realtime full-duplex voice frontend that drives a `kimi acp` session hands-free (barge-in, local wake word); point its generic ACP backend at Kimi Code with `ACP_COMMAND=kimi` and `ACP_ARGS=["acp"]`. |
There was a problem hiding this comment.
When a reader follows this qwen-audio-agent setup as written, ACP_COMMAND and ACP_ARGS are ignored unless qwen-audio-agent is first told to use the generic ACP backend. Its setup docs show the generic path as AGENT_PROTOCOL=acp together with ACP_COMMAND/ACP_ARGS (https://github.com/QwenAudio/qwen-audio-agent/blob/main/README_EN.md#L399-L404), while an empty protocol runs frontend-only, so the example will not actually start kimi acp for users who copy just this paragraph; the Chinese README has the same omission.
Useful? React with 👍 / 👎.
1 participant
Related Issue
No issue — docs-only change (README clarification), per CONTRIBUTING doc changes may be submitted directly.
Problem
The README's "Use it in your editor (ACP)" section implies ACP usage is limited to editors. Since Kimi Code supports ACP over stdio (
kimi acp), non-editor ACP clients — like voice frontends — can also drive it, but the README gives no example of this.What changed
Added one short paragraph to the ACP section of both
README.mdandREADME.zh-CN.md, noting that ACP clients are not limited to editors and giving a concrete voice example: qwen-audio-agent (an ACP client list is maintained on the official ACP site). No code changes.Disclosure: I'm a maintainer of qwen-audio-agent.
Checklist
gen-changesetsskill, or this PR needs no changeset. (No changeset needed — README only)gen-docsskill, or this PR needs no doc update. (The README change itself is the doc update)