install: Qwen Code hooks + MCP connector - #25
Conversation
…~/.qwen/settings.json
|
This branch is cut from a pre-09-03 base, so beyond the Qwen additions its diff against current
The red The six genuinely-Qwen hunks have been re-applied on top of current canonical in davidcrowe/agenticcontrolplane.com#145 (+75/−1, Suggested order: merge and deploy #145 → resync this mirror from canonical → close this PR rather than merging it, since its content is by then either landed or a regression. |
|
Correction to the comment above. It said merging this PR would revert the codex-acp work. That was wrong — it was read off What is actually true about this PR:
The Qwen hunks are re-applied on current canonical in davidcrowe/agenticcontrolplane.com#145 (POSIX-clean). Suggested order is unchanged: merge + deploy #145 → resync this mirror from canonical → close this PR, since by then its content is landed. |
…+ Qwen Code block
Adds Qwen Code (QwenLM/qwen-code, ~27.6k stars, ~85k npm downloads/week) as a hooked client.
~/.qwenorqwenon PATH.PreToolUse/PostToolUseentries into~/.qwen/settings.jsoncalling the sharedgovern.mjswithACP_CLIENT=qwen-code. Qwen's hook contract is Claude Code's (same stdin fields,hookSpecificOutput.permissionDecision, exit 2 blocks); two deltas handled: timeout is milliseconds (5000), matcher*= every tool.mcpServersin the same file; warns ifdisableAllHooksis set.Verified 2026-09-03 with the same settings shape inside a fresh Linux container (Harbor, Qwen Code 0.23.0): hook fired on the first tool call, session recorded under client
qwen-codein the runs API. Pages: agenticcontrolplane.com PR #133.