[Bug] Qwen Code > Run in VS Code Command doesn't run well on WSL - Need to re run manually as far it's terminal in vs code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 3.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 714
Description
What happened?
See the video here. When we choose the Qwen > Run, it run the command twice, but just opening bash wsl, We need to manually run the qwen once more.
https://github.com/user-attachments/assets/e3babe90-ff7e-45e7-96e0-b9f114849c03
What did you expect to happen?
Works like in native linux, one time run, it run and detect the opened files.
Client information
$ qwen /about About Qwen Code
│ │
│ CLI Version 0.0.9 │
│ Git Commit 600c58bb │
│ Model qwen3-coder-plus │
│ Sandbox no sandbox │
│ OS linux │
│ Auth Method qwen-oauth
Login information
CLI, no API, using oAUTH
Anything else we need to know?
Fedora 42 WSL, Windows 11 24H2, last time I need to add qwen --ide-mode-features, not it just works to see opened files, just sadly, it doesn't work in WSL for invoking 1st time running
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the VS Code Qwen > Run flow on Fedora 42 under WSL and compare it with native Linux, using the attached video and reported CLI version as context. Done means the command launches once, runs without manual re-entry, and detects opened files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- cli, developer-experience, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100