← GUI catalog

Harness-native GUI

Qwen Code Desktop

The first-party Qwen Code desktop shell with multi-session and split views, optional worktrees, visual Git diffs, and a bundled local runtime.

Status
Active
License
Apache-2.0
Source access
Open source
Record checked

At a glance

Qwen Code users who want the first-party visual workflow on macOS, Windows, or Linux without installing the CLI separately.

Good choice if

Qwen Code users who want the first-party visual workflow on macOS, Windows, or Linux without installing the CLI separately.

Check before choosing

The current thin shell is intentionally local, single-window, and single-workspace at a time; remote backends and shared teammate access are not desktop capabilities.

Workflow fit

Existing evidence gates classify four predefined workflows. Bands are non-numeric and do not rank product quality.

  • One agent + review

    Strong fit

    Stay close to one coding session and inspect changes in a dedicated visual surface.

    Current sources document visual review, workspace isolation.
  • Parallel local tasks

    Strong fit

    Run several coding tasks on one machine without their branches or files colliding.

    Current sources document parallel sessions, workspace isolation, visual review.
  • Remote control

    Not eligible on current evidence

    Start or revisit coding work away from the machine where the repository is running.

    The product is inactive or a required mechanism is contradicted by current evidence.
  • Shared team workspace

    Not eligible on current evidence

    Let teammates enter the same live workspace to watch, steer, preview, or review work.

    The product is inactive or a required mechanism is contradicted by current evidence.

Harness coverage

The desktop package embeds the Qwen Code CLI runtime and reuses its Web Shell. Provider breadth inside Qwen Code is model routing, not support for another coding harness.

1 named integration
  • Qwen Code

Workflow mechanisms

Unknown means the current first-party record does not establish the mechanism; it is not converted into evidence of absence.

3 of 5 documented
  • parallel sessions

    Documented

    The shared Web Shell can select multiple sessions and display them concurrently in an in-window split view.

  • workspace isolation

    Documented

    The new-session Git-mode control can create a named Git worktree and root the session in that checkout.

  • visual review

    Documented

    The Web Shell includes a dedicated Git diff dialog with file lists, expandable hunks, additions, deletions, and binary states.

  • remote execution or access

    Contradicted

    The current Desktop design starts an authenticated daemon on a random loopback port and intentionally keeps external URLs outside the app.

  • shared team access

    Not established

    Current first-party Desktop sources do not establish multiple teammates entering the same live workspace.

Technical and public context

Implementation inspection and source-native activity provide investigation context. Neither changes workflow fit.

Inspect implementation record and public activityContext, not workflow fit

Public activity signals

Daily source snapshots provide ecosystem context only. They do not affect workflow fit or capability claims.

1 mapped source

Implementation record

Inspected at commit e1e5b42ce110.

  • The desktop shell embeds the Qwen Code daemon and reuses the first-party Web Shell.
  • The Web Shell implements multi-session split view, selectable Git-worktree mode, and a structured Git-diff dialog.
  • The desktop design constrains the daemon to loopback and the UI to one window and workspace at a time.
Inspected paths
  • README.md
  • packages/desktop-shell/README.md
  • docs/design/2026-07-31-desktop-web-shell-release.md
  • packages/web-shell/client/components/SplitView.tsx
  • packages/web-shell/client/components/GitModePopover.tsx
  • packages/web-shell/client/components/dialogs/GitDiffDialog.tsx

The audit establishes the current local desktop architecture and UI mechanisms, not task quality, security, or reliable cross-platform behavior.

First-party evidence

Sources establish specific current GUI claims; their count does not add fit points.

6 first-party sourcesGUI record checked