Looking for Qwen Code users to help validate Concord integration

[alexechoi]

I'm building Concord, an open-source MCP server for shared work-state between coding agents. It lets agents claim scope, keep shared task context, exchange messages, and leave handoffs across supported harnesses.

We're working toward dedicated Qwen Code support, tracked in this issue. I'd welcome help from someone using Qwen Code day to day to validate the integration rather than assume compatibility from its Gemini CLI ancestry.

The intended workflow also includes coordination between separate Qwen Code sessions, with each keeping its own identity, claimed scope, and shared task context.

A useful first test is checking the current MCP configuration and instruction-loading behavior, then opening two sessions and confirming that they register as distinct Qwen agents in the right repository.

After that, we'd like to test a prompt/reply exchange with an existing supported client and determine which hooks or session APIs can deliver a message while Qwen is busy or idle.

This is a contribution and validation request, not an announcement of completed support. Even a report containing your Qwen Code version, configuration path, and the first failure you hit would help move it forward.

Concord Cloud connects local, remote, and async agents in one shared workspace. Work can continue across machines and at different times, with task context and handoffs available for the next agent. Try Concord Cloud. The integration work above is still needed for this harness to join that workflow.

Would anyone like to try that first session test?