# AI use cases for Minke (lencx/Minke)

Repo: [lencx/Minke](https://github.com/lencx/Minke) | Use cases: 3 | Page: https://dedupedai.com/use-cases/lencx-minke/

Minke is a local-first desktop agent workspace that combines conversations, files, terminals, and a shared browser, powered by DeepSeek Harness.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Continue agent tasks from your phone over Tailscale: https://dedupedai.com/use-cases/lencx-minke/reach-minke-from-phone-over-tailscale/
- Run Minke in development mode from a source checkout: https://dedupedai.com/use-cases/lencx-minke/build-minke-from-source-for-development/
- Check a Minke installer against published SHA-256 digests: https://dedupedai.com/use-cases/lencx-minke/verify-minke-download-before-install/

## How to continue agent tasks from your phone over Tailscale with Minke

Repo: [lencx/Minke](https://github.com/lencx/Minke) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Expose Minke's Web UI privately to your phone through Tailscale Serve over HTTPS.

**Who it is for:** A developer who starts agent tasks on a home or office computer and wants to check progress or send follow-up requests from a phone on the same tailnet.

**The problem:** The Minke workspace runs on one computer, so it is not reachable from a phone while you are away from the desk.

**The outcome:** The phone opens a secure HTTPS address for Minke, where you can continue conversations, start tasks, manage project files, and use a terminal that runs on the Minke computer.

### Steps

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 Connections → Device access → Remote access, select HTTPS Serve, and enable remote access; no restart is required.
3. Copy or open the displayed https://…ts.net address on the phone.
4. On the phone, open the address, choose Install Minke in the sidebar, and accept the browser install prompt to add it as a PWA.

### Prompt to paste into your agent

```text
Using the lencx/Minke repository README, guide the user through enabling Tailscale Serve remote access on a computer running Minke and confirm the displayed https://…ts.net address. Expected output: a short checklist with the address the phone should open. Verify that the Tailscale status on the Minke computer shows it connected to the same tailnet as the phone before reporting success.
```

### Caveat

Tailscale Direct IP uses HTTP and is not a browser secure context, so the README recommends Tailscale Serve for most setups.

Risk, credentials: The remote page can start agent tasks and use local tools already authorized in Minke, so only add trusted tailnet members as users.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/lencx-minke/reach-minke-from-phone-over-tailscale/

## How to run Minke in development mode from a source checkout with Minke

Repo: [lencx/Minke](https://github.com/lencx/Minke) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

Stage the pinned DeepSeek Harness runtime and launch the Minke development app.

**Who it is for:** A developer who wants to read, modify, or contribute to Minke and needs a working development build on their own machine.

**The problem:** Minke's runtime depends on a pinned DeepSeek Harness source, so a fresh checkout does not run until the runtime is prepared.

**The outcome:** A local development Minke window opens, with desktop settings and Harness data kept in separate work/development directories that Git ignores.

### Steps

1. Clone https://github.com/lencx/Minke and initialize the vendor/deepseek-harness submodule with `git submodule update --init`. (inferred, check the README)
2. Install the repository dependencies with pnpm 11.28.5 on Node.js 24 or newer.
3. Run `pnpm run harness:stage` to install and build the pinned DeepSeek Harness source and stage the runtime under runtime/host.
4. Run `pnpm start` to refresh the Minke integration and launch the development app.

### Prompt to paste into your agent

```text
Using the lencx/Minke repository, set up a development build from a fresh checkout and report the result of each step. Expected output: a log summary showing that harness:stage completed and that pnpm start launched the app. Verify that the vendor/deepseek-harness submodule is populated before running any build command.
```

### Caveat

The README says the build must run on the same operating system and CPU architecture as the package you need, and cross-platform packaging from one host is not supported.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/lencx-minke/build-minke-from-source-for-development/

## How to check a Minke installer against published SHA-256 digests with Minke

Repo: [lencx/Minke](https://github.com/lencx/Minke) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Confirm a downloaded Minke package matches the official release checksums before installing it.

**Who it is for:** A security-conscious user or IT admin who must confirm a downloaded installer came from the official Releases page before running it.

**The problem:** Pre-release builds are not notarized, so the README asks users to download only from the official Releases page and a checksum check adds a second confirmation.

**The outcome:** The user knows whether the downloaded package matches the digest listed in the official SHA256SUMS file.

### Steps

1. Download the package for your platform from the official Minke Releases page.
2. Download the release checksums from https://github.com/lencx/Minke/releases/latest/download/SHA256SUMS.
3. Compute the package digest with `shasum -a 256 <package-file>` on macOS or Linux. (inferred, check the README)
4. Compare the output with the matching line in SHA256SUMS and install only if they match. (inferred, check the README)

### Prompt to paste into your agent

```text
Using the lencx/Minke README and its SHA256SUMS release file, verify the SHA-256 digest of the downloaded <package-file>. Expected output: a match or mismatch report for that exact filename. Verify that the filename in SHA256SUMS matches the downloaded package name before comparing digests.
```

### Caveat

The README publishes SHA256SUMS but does not give a verification command, so the commands in this use case are a general approach rather than a documented Minke step.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/lencx-minke/verify-minke-download-before-install/