Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The official GitHub Release published_at is 2026-09-10T08:04:06Z, or 16:04:06 Beijing time. This page does not substitute tag creation time for publication time.
- v0.3.0 retains pending permission/question items when loading a refreshed session, but official notes do not promise to restore items already lost before the upgrade.
- The Windows fix releases the node-pty conout worker after each PTY ends. Validate processes and handles when creating terminals, completing tasks and exiting the app.
- The web-shell workspace provider gains self-diagnostics and reload on root retry; still verify the actual workspace root and file permissions.
- The official Release provides Windows x64, macOS arm64/x64, Linux AppImage/deb, SHA256SUMS.txt and signature files. Stop installation immediately if architecture or verification does not match.
- PRODUCT_FIT=CONDITIONAL_NETWORK_ONLY: version, permission state, PTY cleanup and workspace-root errors are not proxy issues. Compare egress only with evidence of DNS, TLS, 407 or connection timeouts.
What changed: a desktop update spanning permissions, terminals, errors and workspaces
QwenLM published Qwen Code Desktop v0.3.0 on its official GitHub Release page. The Release API records publication at 2026-09-10T08:04:06Z, with tag `desktop-v0.3.0` and commit `b74592785bff038a1e3b5c533d20ae49e549ab2a`. The focus is desktop workflow state retention and diagnosability, not a new model.
Official changes retain pending permission/question items after session refresh, preserve Responses-stream error details, release the Windows node-pty conout worker after each PTY, and add web-shell workspace-provider self-diagnostics and reload on root retry. No affected-user count was published, nor a guarantee covering every third-party provider, old session or custom installation method. Those scopes remain UNKNOWN.
Match the symptoms: do not collapse four failures into “the desktop app is broken”
The first symptom is a pending file or command permission or clarification question disappearing after session refresh or restoration. The second is leftover Windows workers, slow exit or growing resources after repeated PTY creation and closure. The third is a vague Responses-stream failure that obscures authentication, parameters, quotas or service status. The fourth is web-shell failing to recognize the workspace root and remaining stale after retry.
Record desktop version, operating system and architecture, session ID, absolute workspace path, reproduction steps, original error, time, whether refresh occurred and whether the task may already have run. For permissions, record the pending action; for terminals, task start and completion; for streams, request/run ID; for workspaces, root and file permissions. Without this evidence, a successful upgrade cannot establish the old problem’s root cause.
Before upgrading: protect sessions, configuration and unconfirmed actions
Stop new tasks that write files, commit code or call external systems, and wait for started actions to reach a verifiable terminal state. Screenshot or inventory each pending permission/question, save uncommitted diffs, important conversation exports, workspace paths and user configuration. For unknown action status, inspect files and external systems first; a vanished confirmation dialog after refresh is not grounds to rerun immediately.
Choose reproducible examples without external side effects: a read-only command permission prompt, a cancellable long terminal task, a Responses request producing a clear test error and a non-production workspace root. Record the same results on the current version as the post-upgrade baseline.
Choose and verify the official Release package; do not guess the auto-update path
The official v0.3.0 Release provides Windows x64 setup.exe, macOS arm64/x64 dmg, Linux amd64 AppImage/deb, plus `SHA256SUMS.txt` and corresponding `.sig` files. Select only Assets matching your operating system and CPU architecture from that Release. Unless the page or app explicitly confirms auto-update completion, a restart alone does not prove the version changed.
After downloading, verify against `SHA256SUMS.txt`, then inspect the signature file and source URL. Confirm no task is running or has unknown status before closing the desktop app, then install through an organizationally permitted method. Retain installer name, size, hash, installation time and old version. Stop immediately for architecture mismatch, failed verification, abnormal signatures, redirects to unofficial domains or security-software warnings.
Validate the four fixes with the same actions
For permissions, create a test session with a read-only permission prompt and a clarification question, refresh without approving, and confirm both remain pending without duplicate execution. For Windows PTY, create and normally finish several short tasks, confirm conout workers do not persist after exit, and verify the app can still create terminals. Forced process termination is not normal cleanup.
For Responses, use a test request to trigger an expected error and confirm the UI or logs retain enough detail to distinguish authentication, parameters, quotas and service status, without logging sensitive tokens. For workspaces, make a controlled retry from an incorrect root, confirm the provider supplies diagnostic information and reloads after the correct root is selected, then validate the read-only access scope without expanding file-write permissions.
Failure layers, stop conditions and rollback
If pending items still disappear, distinguish old pre-upgrade sessions, refresh-method differences and actions already completed. For lingering PTYs, record Windows version, parent/child processes and a minimal reproduction. For vague stream errors, retain provider, model, request/run ID and original status. For failed root retries, check absolute path, directory existence, file permissions and workspace-provider logs. Avoid repeated reinstalls across unrelated layers.
Stop expanding the rollout immediately for package-check or signature anomalies, lost session content, expanded default permissions, duplicate writes, continuing terminal-resource growth or inaccessible critical workspaces. If the organization retains a verified old installer and configuration snapshot, roll back and continue with manual confirmation or restricted read-only workflows. Rollback cannot restore already lost data; reconcile external actions with unknown status separately.
Network boundary: fix versions and permissions first; compare egress only with connection evidence
Lost permission/question items after refresh, unreleased Windows node-pty workers, missing Responses error details and workspace-root reload behavior are client-state or version issues. Do not address them by changing IPs, disabling TLS verification or expanding proxy permissions. Fixed egress cannot replace the correct installer, file permissions or user confirmation.
Use the layered proxy connection troubleshooting checklist only for DNS resolution failures, TLS handshake errors, proxy 407 responses, connection timeouts when accessing GitHub Releases, model APIs or organizational services, or stable differences reproducible with the same account and configuration across egress routes. Preserve request/run ID and target domain first. If symptoms remain after connectivity recovers, return to the version, session, permissions and workspace layers.
Sources
- QwenLM GitHub Release: Qwen Code Desktop v0.3.0
- Qwen Code PR: preserve pending permissions and questions after session refresh
- Qwen Code PR: preserve Responses-stream error details
- Qwen Code PR: release conout worker after Windows PTY completion
- Qwen Code PR: workspace-provider self-diagnostics and root-retry reload
- PuppyIP: layered proxy connection troubleshooting checklist
Frequently Asked Questions
When was Qwen Code Desktop v0.3.0 released?
The official GitHub Release API published_at is 2026-09-10T08:04:06Z, or 16:04:06 Beijing time. The tag was created earlier; its creation time is not the official publication time.
Will permission prompts still disappear after refresh?
The official v0.3.0 change retains pending permission/question items during refreshed session load. Retest in a non-production session first; no promise was made to restore items lost before upgrading.
Is node-pty always responsible for a stuck Windows terminal?
No. v0.3.0 fixes conout-worker release after each PTY. Use parent/child processes, final task state, logs and repeatable steps to exclude the command itself, antivirus or file-permission issues.
Which installer should I download?
From official v0.3.0 Release Assets, select Windows x64 setup.exe, macOS arm64/x64 dmg or Linux amd64 AppImage/deb for your system and architecture, then verify SHA256SUMS.txt and the signature file.
What if the workspace root still will not open after updating?
Save provider self-diagnostics, check the absolute path, directory existence and file permissions, then perform a controlled retry/reload on the correct root. Do not hide path errors by granting whole-disk permissions or repeatedly reinstalling.
Can a fixed IP repair these problems?
It cannot repair client state, permission retention, PTY cleanup or root reload. Network comparison is meaningful only with evidence of DNS, TLS, 407, connection timeouts or consistent differences between egress routes.