Skip to content

[feat] desktop D1: Desktop application #363

Open

Description

@FayeSpica

Goal and scope

D1 under RFC #362 and roadmap #265. Deliver an Electron desktop shell around the existing Web UI and Python business services, runnable without development tools.

Design

Follow the shell/Host lifecycle pattern in DeepSeek Harness Desktop, adapted to OpenDirector:

  • Host lifecycle: Electron owns a bundled Python API process bound to 127.0.0.1 on an OS-assigned port. A private control channel reports starting, ready, fatal and shutdown completion. Show actionable startup errors and log locations.
  • Authentication: Generate a fresh credential per Host launch, held by the main process and Host. Attach it only to requests for that Host; exclude it from renderer code, URLs, logs and shared localhost cookies.
  • UI and native operations: Reuse the Web UI in an isolated, sandboxed renderer with Node integration disabled. Expose validated preload IPC for file dialogs, saving and window operations. Keep business commands and validation in the shared Python services.
  • Runtime and data: Bundle Python, dependencies, FFmpeg and the built-in Agent runtime. Keep application resources read-only and separate from projects, credentials, logs and caches. Preserve existing data; desktop and CLI share project identity, locks and revisions.
  • Shutdown: Repeated launches focus the existing application. Distinguish closing a window from quitting. Inspect Agent, generation and export tasks before quitting, explain interruption risks, and coordinate child-process shutdown. A remote task is not cancelled merely because the application exits.
  • Export: Retain browser rendering initially and keep its renderer alive during export. Hiding a window does not imply export can continue after application exit.
  • CLI: Offer optional command installation, repair and removal using the bundled runtime. Preserve independent CLI installations and update command help.

D1 owns the shared shell, Host protocol, runtime layout and acceptance checks. Platform installation, signing and distribution belong to #364–#366; automatic updates belong to #367.

Acceptance criteria

  • From a packaged build on a clean environment: launch → Agent-assisted creation and tool use → edit → export → reopen, without system Python, Node, npm or FFmpeg.
  • Verify authenticated dynamic-port startup, startup failure, duplicate launches, project locks, task-aware shutdown and recovery diagnostics.
  • Validate the actual bundled executables and Python imports, including Agent startup; dependency files alone do not establish a working installation.
  • Verify Chinese and English interactions and errors; document tested OS versions, architectures and remaining limits.
  • Include reproducible build/check commands and actual packaged-build acceptance evidence in the implementation PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:desktopDesktop integration / 桌面集成

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions