dsh-swiftUI

A native macOS shell for the DeepSeek Harness (dsh) web UI.

dsh ships its product as a CLI that boots a local HTTP server and serves a SPA front-end. dsh-swiftUI wraps that experience in a native SwiftUI application: it owns the window, the menu, the lifecycle, and (by default) forks dsh web itself. The dsh SPA is rendered inside a WKWebView; the native side stays out of dsh's way.

Pure shell. dsh-swiftUI does not modify dsh, does not bundle dsh, and does not write any dsh client plugin. It talks to dsh the same way a browser does: a single HTTP/WebSocket origin on 127.0.0.1.

This first milestone delivers the main panel only — the WKWebView pointing at the dsh SPA, with a transparent titlebar and a floating status badge. The roadmap for future native panels (Git, file tree, in-process terminal) is captured in docs/ROADMAP.md; that work is intentionally deferred.

What works

Requirements

• macOS 15+ (built and tested on macOS 27 with the Xcode-beta SDK)
• Xcode-beta (the bundled Swift 6.4 toolchain is the target compiler)
• A working dsh install — dsh --version should print 0.1.0-rc.6 or later.

  npm install -g @deepseek-ai/dsh

  The first launch needs the dsh front-end dist to be built (pnpm run build from the dsh repo). dsh-swiftUI does not ship the dsh dist.

If you have multiple Xcode versions installed, point the active developer directory at the beta once:

sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer

Building

Option A — Xcode

brew install xcodegen              # one-time
./scripts/generate-xcodeproj.sh    # regenerates DSHShell.xcodeproj
open DSHShell.xcodeproj

Then ⌘R. The first build expects a signing identity. For a local-only build, set the team to "None" and enable "Sign to Run Locally"; the project already disables Hardened Runtime because ad-hoc-signed frameworks would otherwise fail dyld library validation (no shared Team ID).

Option B — Swift Package

swift build -c release           # builds DSHShellCore + DSHShell
swift test                       # runs the 10 unit tests

To produce a .app bundle, use the Xcode project (Option A).

Configuration

Settings live at ~/Library/Application Support/dsh-swiftUI/settings.json. Defaults:

{
  "dshBinaryPath": "/Users/djx/.npm-global/bin/dsh",
  "launchMode": "spawn",
  "listenHost": "127.0.0.1",
  "preferredPort": 0,
  "trustedHosts": ["127.0.0.1", "localhost"],
  "pollIntervalSeconds": 0.5,
  "spawnTimeoutSeconds": 30,
  "autoRestartOnCrash": true
}

The shell forwards no working directory to dsh web — the dsh SPA picks its own workspace inside the browser UI.

Lifecycle

+-----------+   fork    +----------+    http   +-----------+
| DSHShell  | --------▶ | dsh web  | --------▶ | WKWebView |
| (macOS)   |           | (child)  |           |  + SPA    |
+-----------+           +----------+           +-----------+
       │                      │
       │  ⌘Q / terminate    │  crash
       ▼                      ▼
   kill+waitpid         respawn w/ backoff

• On launch the app forks dsh web, captures the dsh web: http://127.0.0.1:NNNN/ line, and points the WKWebView at it.
• If the child crashes, the manager schedules a single automatic restart with exponential back-off (capped at 30s).
• On applicationWillTerminate the AppDelegate calls AppCoordinator.shutdownBlocking(): it signals the child with SIGTERM, escalates to SIGKILL after 5s, and uses waitpid to confirm the child has reaped before the process exits. This is the path that prevents orphan dsh processes — a Swift Task would not have run in time during runtime teardown.

Diagnostics

Lifecycle events flow through OSLog with subsystem ai.deepseek.dsh-shell. To see them:

log stream --predicate 'subsystem == "ai.deepseek.dsh-shell"' --info --debug

Or read the last minute:

log show --predicate 'subsystem == "ai.deepseek.dsh-shell"' --last 1m --info --debug

If a launch fails with EADDRINUSE, a previous dsh web is still bound to a port. The error message tells you to run pkill -f 'dsh web'.

Architecture

See docs/ARCHITECTURE.md for the layered view, the dsh integration boundary, the process model, and the App Sandbox stance. The roadmap for native panels lives in docs/ROADMAP.md.

License

MIT. See LICENSE.