DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

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

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

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

What you need first

  • A macOS, Windows x64, or Linux x64 computer
  • Access to the official GitHub Releases page for Minke
  • For remote access: a Tailscale account and Tailscale installed on the Minke computer and the phone
  • For building from source: Git with submodule support, Node.js 24 or newer, and pnpm 11.28.5

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page