feat: add a link to Gemini CLI Desktop for Qwen Code users who prefer desktop UIs

[bl-ue]

We've developed a desktop/web UI for Qwen Code and other Gemini CLI-based tools called Gemini CLI Desktop. I'm adding a link to it to Qwen Code's README to provide Qwen Code to a larger audience—users who prefer desktop UIs and users who need to access Qwen Code remotely with a web-based UI.

[bl-ue]

Hi @pomelo-nwu! Would you be interested in merging this PR?

[pomelo-nwu]

Hi @bl-ue, Thank you for your contribution! Adding web and desktop capabilities as an extension to the CLI tool sounds like a great ecosystem integration.

I just tried to download it, but I couldn't find a software package compatible with my machine (Apple M2 Pro ). Could you please provide me with a download link for ARM64 macOS so I can test it out? Once I've verified it works well, I'd be happy to add your software to Qwen Code's integration ecosystem.

Also, I apologize for the delayed response to your PR. We recently stopped syncing with the upstream Gemini CLI repository and now have a stable version of our own. This has given us the opportunity to review community PRs more carefully.

To keep better track of future updates and collaborations, feel free to join our developer channel: https://app.slack.com/client/T09R7UY3FT2/C09QSH4FDUZ

Looking forward to testing Gemini Desktop and potentially merging this PR! 🚀

[bl-ue]

@pomelo-nwu Thank you! You're very kind. The desktop app's ARM builds are named aarch64, which is probably why you didn't see it. Please use this link: https://github.com/Piebald-AI/gemini-cli-desktop/releases/download/v0.3.12/GeminiCLIDesktop_0.3.12_aarch64.dmg.

If the qwen command is in your PATH and you've authenticated with it previously, Gemini CLI Desktop (called Qwen Code Desktop when Qwen Code is selected in the settings) should automatically work perfectly for you.

[pomelo-nwu]

@bl-ue “Gemini CLI Desktop” is damaged and can’t be opened.

[bl-ue]

@pomelo-nwu I forgot about that! We aren't codesigning the macOS or Windows binaries yet.

We've actually already purchased a codesigning certificate to sign Piebald on Windows, and when we get it we'll use it for Gemini CLI Desktop too. We're undergoing validation for Apple's Developer program, so we'll get a codesigning certificate for macOS soon as well.

In the meantime, first drag the app into Applications, and then you can "ad hoc" sign it for just your machine with this command:

codesign -s - "/Applications/Gemini CLI Desktop.app"

(Colleagues would need ad hoc sign it themselves in the same way, since it's tied to the machine you do it.)

[bl-ue]

Hi @pomelo-nwu! I'm sorry about the delay. We've codesigned the macOS and Windows builds of Gemini CLI Desktop; please try version 0.3.14: https://github.com/Piebald-AI/gemini-cli-desktop/releases/download/v0.3.14/GeminiCLIDesktop_0.3.14_aarch64.dmg

[pomelo-nwu]

@bl-ue Nice work! I just tried the download, but it seems to be stuck at the connection stage. Is this potentially a compatibility issue with qwen code v0.4.0 (my current version)?

[bl-ue]

@pomelo-nwu That's unfortunate! The theory that it might be because of v0.4.0 is a great one, but I just tested the app with QC 0.4.0 and it worked fine for me. Will you please try running the binary directly in the terminal, save the logs to a file after it's been hanging for a while, and then upload it here? The command should be something like /Applications/Gemini\ CLI\ Desktop.app/Contents/MacOS/gemini-cli-deskop Thank you!

[mike1858]

@pomelo-nwu this can happen sometimes - running qwen in the terminal once should fix it. If you can reproduce it, the logs would be helpful. Otherwise, that should fix it.

[pomelo-nwu]

@bl-ue @mike1858 After restarting Qwen, I can use it and everything looks great. I noticed the text appeared too early in the document, so I've merged it for now and will sort out the README placement in a bit.

[mike1858]

@pomelo-nwu Great to hear it worked!