One-Sentence Positioning

This is a Web platform smoke testing fixture bundled with the Minke desktop project, serving as a minimal external Web plugin that plugs into the host's renderer module loader to verify that the dsh plugin installation and hot-update pipeline is functioning properly.

Core Capabilities

• Writes data-dsh-external-web-plugin="active" on the host page's HTML root element as a probe marker for "external Web plugin loaded"
• Registers itself as a client module that can be started by the host via the host-provided window.__ModuleLoader__
• Declares a cordis patch in the package metadata to insert itself into the host's startup list with the name @dsh-desktop/smoke-web-plugin
• Does not do anything in the desktop main process; the main process-side apply() is an empty function

Technical Implementation

• Language: JavaScript (ESM, type: module)
• Key Dependencies: Only depends on the host runtime's window.__ModuleLoader__, no third-party dependencies
• Architecture Pattern: Web platform client plugin—inserts itself into the host's startup list via cordis.patch.yml, then gets loaded by the host in the renderer to register the factory from lib/client.js
• Entry Files: lib/index.js (main process side, empty implementation) / lib/client.js (renderer side, actually effective)

Use Cases

Suitable for Minke maintainers or DSH desktop host developers to verify that the "external Web plugin installation + renderer loading + hot-update" pipeline still works after modifications; not suitable for regular end users to install and use.

Prerequisites and Compatibility

Installation

dsh plugin --profile web add github:lencx/Minke/tests/fixtures/web-plugin

Configuration

This plugin requires no additional configuration. The package's dsh.client only declares three manifest fields and exposes no runtime parameters that can be adjusted by users:

FAQ

Q: What functionality can I see on the DSH desktop after installing this plugin?

A: You won't see any new functionality. Its only side effect is writing a data-dsh-external-web-plugin="active" data attribute on the host page's root element, which regular users cannot perceive as any UI change.

Q: Is it suitable for regular users to install?

A: No. It's a smoke testing fixture within the Minke repository, used by scripts/harness/smoke.mjs to automatically verify the external Web plugin installation and hot-update pipeline. It has no business value.

Q: Can it be uninstalled after installation?

A: Yes, uninstall it using the standard dsh plugin remove process; after uninstallation, the data-dsh-external-web-plugin="active" marker on the host page's root element will disappear.

Q: What does its main process and renderer do?

A: The main process-side lib/index.js exports an empty apply() and does nothing; the real action happens in the renderer, where lib/client.js calls window.__ModuleLoader__.load to register a factory, and the factory's apply() writes the data attribute to the document root element.

Q: How do I verify if this plugin is correctly loaded by the host?

A: In the browser developer tools, inspect the page's root <html> element; if the value of data-dsh-external-web-plugin is "active", it has been loaded. Minke's smoke test also modifies the client source code to change "active" to "reloaded" to verify hot-update.

Getting Started Difficulty

Beginner — the entire plugin consists of only two empty JS files plus a cordis patch. The understanding threshold comes from DSH Web plugin manifest field conventions, not from the plugin's own logic.

Known Issues and Limitations

• Only exists as a smoke testing fixture within the Minke project, does not declare version compatibility information for external use, and cannot guarantee availability in third-party environments
• The main process apply() is always an empty function and cannot extend business logic on the Node/desktop main process side

Minke

A native desktop workspace for DeepSeek Harness

English · 简体中文

Minke brings DeepSeek Harness to the desktop as a focused, local-first workspace for agentic work. Conversations, project files, terminals, web tools, and native desktop actions stay within reach—without fragmenting your workflow across multiple apps.

[!IMPORTANT] Minke is under active development. Features, packaging, and the local data schema may change as the project evolves. Minke is an independent community project, not an official DeepSeek product.

Highlights

• More than a chat window — Independent right and bottom Tabs keep Files, Terminal, Browser, Plugins, and Session details beside the active conversation. The Plugins workspace supports GitHub discovery, installation, status checks, repair, and removal. Files supports navigation, syntax-highlighted previews, editing, and diffs, while Terminal connects to a real PTY on the Minke host.
• A real remote workspace, not screen sharing — Minke Host projects supported desktop capabilities into a responsive Web UI. From a phone or tablet you can continue conversations, start agent tasks, work with project files, and use the host terminal without streaming pixels from the Electron window.
• Installable as a PWA — Open Minke through a secure HTTPS address and install it to the home screen for a standalone, app-like experience. The PWA provides branded launch surfaces and early connection feedback, while deliberately avoiding caches of authenticated workspace traffic.
• Private remote access — Minke can expose its responsive workspace through an application-managed remote route. The currently validated path is Tailscale Serve over HTTPS; Tailscale Direct IP and Cloudflare Access integrations remain experimental until they complete release testing.
• Local model integrations — Minke can discover and connect to LM Studio, Ollama, and other loopback OpenAI-compatible services. Optional lifecycle management can start supported local runtimes when needed without taking ownership of services that were already running.
• Fast keyboard-driven control — The global Command Palette (Mod+K), configurable shortcuts, native menus, Session history navigation, log export, synchronized themes, and English and Chinese UI keep common actions close at hand.
• Safe, recoverable data migration — Choose where Minke stores its data, then preview and merge existing Sessions, plugins, and settings. Minke deduplicates identical files, preserves conflicts and source directories, and switches only after the restart-time migration succeeds; starting with a clean data home remains an option.
• Local-first and cross-platform — Application state and browser session data stay on your machine under the Minke data boundary. Automated releases target macOS, Windows, and Linux, including a portable AppImage.

Mobile access with Tailscale

Minke remote access is a responsive Web client backed by Minke Host—not a video stream or touch-controlled projection of the Electron window. From a phone you can continue conversations, start agent tasks, manage project files, and use a terminal that runs on the Minke computer.

[!NOTE] The only remote route currently tested end to end is Tailscale Serve over HTTPS. Tailscale Direct IP and Cloudflare Access are available as advanced integrations, but have not yet completed release validation and should be treated as experimental.

Minke can expose its Web UI privately through Tailscale Serve. It keeps Harness on the local loopback address, does not bind it to the LAN, and does not enable the public Tailscale Funnel.

1. Install Tailscale on the Minke computer and the phone, sign both into the same tailnet, and confirm the computer is connected.
2. In Minke, open Settings → Remote access, enable Access through Tailscale, then choose Restart Minke when prompted.
3. Return to Remote access, then copy or open the displayed https://…ts.net address on the phone.

Install as a PWA

Open the Tailscale HTTPS address, choose Install Minke in the sidebar, and accept the browser install prompt. On iPhone or iPad, use Share → Add to Home Screen. The installed app launches in standalone mode; when connectivity is poor it shows connection or offline feedback instead of silently presenting cached workspace content.

Minke owns a foreground Serve session and stops it when the app exits. The remote page can start agent tasks and use local tools already authorized in Minke, so grant tailnet access only to people you trust.

Installation

Download Minke only from the official GitHub Releases page. The links below always point to the latest stable release.

Release checksums are available in SHA256SUMS.

macOS

1. Download the .dmg file and open it.

2. Drag Minke.app into the Applications folder.

3. Current pre-release builds are not notarized. Open Terminal and remove the quarantine attribute from the installed app:

   xattr -dr com.apple.quarantine "/Applications/Minke.app"
   

4. Open Minke from the Applications folder.

[!CAUTION] Removing the quarantine attribute bypasses a macOS security check. Run this command only for Minke.app downloaded from the official Releases page, and never replace the path with a broad directory. You can also try Apple's Open Anyway flow under System Settings → Privacy & Security.

Windows

1. Download the Windows x64 .exe installer.
2. Run the installer and follow the on-screen instructions.
3. Windows may show a reputation-based warning for a new pre-release build. Continue only after confirming that the installer came from the official Minke Releases page.

Linux

Download the package for your distribution, then open it with your graphical package manager or install it from a terminal.

Debian / Ubuntu:

sudo apt install "/path/to/minke-package.deb"

Fedora / RHEL:

sudo dnf install "/path/to/minke-package.rpm"

Replace the example path with the downloaded package path.

Build from source

Build Minke on the same operating system and CPU architecture as the package you need. The build produces distributables for the current host under out/make; this project does not support cross-platform packaging from a single host.

Prerequisites:

• Git with submodule support. The vendor/deepseek-harness submodule must be checked out.
• Node.js 24 or newer.
• pnpm 11.7.0, with the repository dependencies installed before running the scripts.
• macOS: an Apple Silicon or Intel Mac with Xcode Command Line Tools. The .dmg target can only be built on macOS.
• Windows: a Windows x64 host. Visual Studio 2022 Build Tools with the Desktop development with C++ workload may be needed if a native dependency must be compiled locally.
• Linux: a Linux x64 host with a native build toolchain, fakeroot, dpkg, and either rpm or rpm-build.

On a fresh checkout, first install the repository dependencies, then prepare the Harness runtime:

pnpm run harness:stage

This command installs and builds the pinned DeepSeek Harness source, then stages the reusable desktop runtime under runtime/host. Run it after a fresh checkout, or whenever the pinned Harness source or runtime contract changes.

Start Minke in development mode with:

pnpm start

pnpm start refreshes the Minke integration in the prepared runtime and launches the development app.

Create the distributable package for the current platform with:

pnpm make

pnpm make performs a full runtime stage again before writing the platform package to out/make.

中国用户

如在使用中遇到问题，或希望进一步交流 Minke，可关注公众号「浮之静」，发送 dsh 获取进群码。也欢迎大家贡献 PR 或分享给更多朋友，您的每一次 Star 都是对开源项目的巨大支持，感恩。