Configuration

On first run the app looks for a DeepSeek Harness checkout in the usual places (~/Workspace, ~/Projects, ~/Developer, ~/src, ~/code, ~). If your project lives elsewhere, or you want to launch something entirely different, open Preferences (⌘,).

Settings are stored as JSON at ~/.config/dsh-launcher/config.json:

{
  "repo": "/Users/you/Workspace/deepseek-harness",
  "command": "pnpm dsh web --no-open --port {port}",
  "port": "3080",
  "browser": "Google Chrome",
  "logFile": "/tmp/dsh-web.log"
}

Field	Meaning
`repo`	working directory the command runs in
`command`	the launch command; `{port}` is substituted
`port`	the port to watch, and to substitute into the command
`browser`	app name to open, or `""` for the system default
`logFile`	where the server's stdout/stderr is written

Because it is just a command in a directory, it happily runs npm run dev, vite, python -m http.server, or anything else.

Why a launch flag matters

The stock command uses --no-open because DSH otherwise opens the URL in the system default browser. Suppressing that and opening the browser here is what lets you use Chrome while Safari remains your system default.

dsh-menubar-launcher

AI 分析

インストール

ドキュメント

Configuration

Why a launch flag matters