What happened?
Qwen Code Desktop became unusable for me because every workspace suddenly turned untrusted / read-only, including the primary workspace.
The UI gives no practical way to recover from this state. I tried resetting the trust configuration, removing saved trust files, resetting the Desktop state, restarting the app, and re-enabling folder trust. Nothing changed.
The application can still see the projects, but refuses to let me work with them. For a coding tool, this is a critical failure because the core workflow becomes inaccessible.
What makes this especially frustrating is that the trust mechanism is not transparent in the UI, and there is no clear recovery path when it gets stuck.
Until workspace trust can be reliably managed and repaired from the Desktop interface, I would not use Qwen Code Desktop for important projects.
Environment: Windows, latest Qwen Code Desktop version at the time of writing.
What did you expect to happen?
I expected Qwen Code Desktop to keep my existing workspaces accessible and writable. Instead, every workspace suddenly became untrusted / read-only, including the primary workspace, with no working recovery option in the UI.
Client information
Client Information
Run qwen to enter the interactive CLI, then run the /about command.
$ qwen /about
# paste output here
Login information
No response
Anything else we need to know?
No response
What happened?
Qwen Code Desktop became unusable for me because every workspace suddenly turned untrusted / read-only, including the primary workspace.
The UI gives no practical way to recover from this state. I tried resetting the trust configuration, removing saved trust files, resetting the Desktop state, restarting the app, and re-enabling folder trust. Nothing changed.
The application can still see the projects, but refuses to let me work with them. For a coding tool, this is a critical failure because the core workflow becomes inaccessible.
What makes this especially frustrating is that the trust mechanism is not transparent in the UI, and there is no clear recovery path when it gets stuck.
Until workspace trust can be reliably managed and repaired from the Desktop interface, I would not use Qwen Code Desktop for important projects.
Environment: Windows, latest Qwen Code Desktop version at the time of writing.
What did you expect to happen?
I expected Qwen Code Desktop to keep my existing workspaces accessible and writable. Instead, every workspace suddenly became untrusted / read-only, including the primary workspace, with no working recovery option in the UI.
Client information
Client Information
Run
qwento enter the interactive CLI, then run the/aboutcommand.Login information
No response
Anything else we need to know?
No response