Getting started

Desktop

Download a qualified installer from GitHub Releases. Release assets may also be served from the configured HTTPS object-storage origin. macOS uses a signed DMG; Windows uses an NSIS EXE. Preview builds can change quickly.

Open Settings → Models and credentials to configure a provider, model and API key. A new profile without model credentials opens the credential guide. Existing usable credentials skip it. Settings → AgentKit Studio → Reopen credential guide opens it again without resetting your configuration.

Create a conversation directly to use DSH Native, or select a Studio Agent to use its frozen runtime configuration. Generated files are delivered through the host's native file cards and sidebar preview.

For a Studio Agent using AgentKit Harness (runtime.type = "harness"), new Revisions and Builds default to the Node-based TypeScript Native engine. No Native opt-in flag, Python environment or uv installation is required. Legacy Harness Builds must be recreated with a Native engine pin. This branch requires the repository's maintained DSH Host interfaces; a public DSH package with the same version is insufficient. An existing desktop release does not automatically contain these changes.

Desktop Settings shows the installed App build, the Studio plugin version and the pinned DSH baseline separately. Update availability compares the installed App build with its channel feed; the version of the plugin package is not the App version.

Development

Use Node.js 22.23.4+ (or Node.js 24.22.1+ / 26.12.1+), pnpm 10.33.2, Git, Make and a native compiler. Keep the official DSH checkout outside this repository:

corepack enable
pnpm install --frozen-lockfile
make setup DSH_ROOT=../deepseek-harness
make dev DSH_ROOT=../deepseek-harness

make setup pins the host, applies reviewed patches, builds it and installs the Studio plugin into the chosen profile. Use a separate DSH_HOME and AGENTKIT_HOME for development. Windows desktop packaging runs on a Windows runner; Make-based Host development on Windows uses WSL2.

Run make doctor DSH_ROOT=../deepseek-harness to check tools, host revision, build outputs and the installed plugin. Credentials belong in Host settings; do not copy profiles or secrets into source files.

The repository keeps browser sources, not generated dist/ files. make dev, make web-dev and make web-start pack and reinstall the current client in DSH_PROFILE before launch. make desktop-dev and make desktop-start rebuild and link this source checkout into the disposable Electron development runtime; set DSH_HOME and AGENTKIT_HOME to disposable directories to isolate these runs. desktop-start reuses an already built DSH Host, while desktop-dev builds it. Electron continues to own its desktop profile. The development runtime resolves Studio from this checkout, outside DSH's isolation boundary for other profiles. Keep DSH_HOME outside both source checkouts (for example a temporary directory or a dedicated directory in your home); the launcher rejects nested profiles. For a plugin linked directly to this source tree, run pnpm build:client after editing sources. pnpm pack always rebuilds the client and includes it in the archive, so users of an installed package need no build tools.