qwen

 qwen-companion

Delegate rescues and code reviews to Qwen Code from inside Claude Code.
One CLI talking to another. No broker, no protocol dance, no magic.

If this saves you an afternoon, star the repo ⭐

---

/qwen:setup
/qwen:rescue investigate why the auth middleware drops cookies on logout
/qwen:review

That's the whole thing. You type a slash command, Claude hands the work over to Qwen Code, and you get Qwen's answer back without Claude paraphrasing it.

---

Table of Contents

• What you get
• Why this exists
• Requirements
• Install
• Usage
  • /qwen:setup
  • /qwen:rescue
  • /qwen:review
  • /qwen:adversarial-review
  • /qwen:status
  • /qwen:result
  • /qwen:cancel
• Typical flows
• Feature parity with codex-plugin-cc
• The --effort flag (how it actually works)
• Qwen integration
• State layout
• Skills that ship with the plugin
• Environment variables
• Development
• FAQ
• Attribution
• License

---

What you get

• /qwen:review — a read-only code review powered by qwen's native /review slash command
• /qwen:adversarial-review — a steerable review with structured JSON findings
• /qwen:rescue — hand any task off to Qwen through a thin subagent
• /qwen:status, /qwen:result, /qwen:cancel — manage background jobs without leaving Claude
• /qwen:setup — health check the runtime and toggle the optional stop-time review gate

Everything is Qwen doing the work. This plugin just makes sure the output comes back to you clean, the state is persisted, and cancellation actually cancels.

---

Why this exists

I wanted codex-plugin-cc's workflow but pointed at Qwen Code.

There's already a qwen plugin floating around built on qwen's --acp (Agent Client Protocol) mode. I tried it, it didn't work for me, so I went looking for a different path.

Qwen's --output-format stream-json turned out to be almost the same shape as the stream-json protocol Claude Code uses internally: a system/init, then stream_event/content_block_delta deltas, then a final result envelope. That made the port easy. It's also way easier to debug than ACP: every event is a newline of JSON, so I can tail -f and pipe through jq while things are misbehaving.

The tradeoff is that every task spawns a fresh qwen process instead of reusing a persistent one. Cold start is 0.5 to 2 seconds. That's invisible for rescue and review workflows and I am not going to over-engineer a broker to save a second per call.

---

Requirements