DSH Desktop DataElement

DSH Desktop packages the local DeepSeek Harness experience as an installed desktop application. It starts Harness automatically, keeps profiles, plugins, workspaces, model settings, and sessions outside the application directory, and opens the full Harness interface as soon as the local runtime is ready. It works with official DeepSeek models or mainstream third-party providers and adds portable Agent presets, phone control for continuing sessions, and editable PPTX generation. What DSH Desktop adds DeepSeek Harness already provides the Agent runtime and Web UI. DSH Desktop adds the native host capabilities needed for a practical desktop product: - Starts and stops Harness without requiring a separate CLI or browser tab - Uses the native system directory picker to add and manage project workspaces - Supports official DeepSeek models and mainstream third-party model providers - Imports and exports complete custom Agent presets as portable .dshpreset packages, with conflict checks and a trust warning before installation - Turns source material into editable PPTX decks through the built-in PPT mode - Preserves profiles, plugins, workspaces, sessions, and model settings across app upgrades - Detects startup and frontend plugin failures, keeps diagnostics in harness.log, and offers guided recovery actions - Provides a non-destructive Safe Mode that temporarily blocks third-party plugins - Lets a paired phone continue sessions over the local network or an optional temporary public tunnel - Checks for desktop updates and keeps download and installation under user control - Adapts native menus, titlebar behavior, window focus, theme, and application branding for macOS and Windows PPT generation Enable the PPT button, choose a template, and describe the deck you need. The built-in catalog includes 16 templates and 192 layouts with editable PPTX output. Previews use English; decks can use English or Chinese, with corresponding font settings. Preview language does not determine output language. PPT is preinstalled, and its automatic instructions apply only to sessions where the PPT button is enabled. See the PPT runtime guide for templates, validation, and source acknowledgments. Phone access Choose Connect Phone… from the Harness menu and scan the pairing code. The desktop asks you to approve the connection before the phone can access sessions. Harness itself remains on a random 127.0.0.1 port. Phone access uses a separate paired bridge. It can stay on the local network or, when you choose remote access, use a temporary Cloudflare Quick Tunnel. Disconnecting the phone from the desktop invalidates the mobile session. If Cloudflare fails to start, the app tries Pinggy. If a Cloudflare pairing link appears but your phone cannot open it, choose Can’t open? Try another link to switch to Pinggy. Safe Mode and recovery If a third-party plugin interferes with startup or rendering, DSH Desktop can identify the implicated plugin from runtime and frontend evidence and open a guided recovery surface. Choose Restart as Safe Mode… from the Harness menu to start an isolated profile containing only official core bundles. The Agent, sessions, model settings, and workspaces remain available while third-party plugins from the normal profile stay blocked. You can remove selected plugins or return to a normal launch from the Safe Mode banner. Recovery screens check for compatible plugin updates. When available, you can upgrade an affected plugin; Safe Mode also offers batch upgrades. For help, hover over WeChat group to display its QR code, or click Discord to open the community. If the normal interface cannot be reached, start DSH Desktop with --safe-mode. On macOS: open -a "DSH Desktop" --args --safe-mode Local data and security - The Harness Web UI is served only on a random loopback port. - The renderer has no Node.js privileges and uses context isolation and sandboxing. - Webviews, untrusted in-app navigation, and unexpected permission requests are blocked. - External web links open in the system browser. - User profiles and sessions live under Electron's per-user application data directory, not inside the installed app. - Phone access requires a short-lived pairing token and explicit desktop approval.