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

How to build the Linux desktop packages yourself from source with DeepSeek Harness Linux

Clone the fork, install dependencies, and produce x64 or arm64 packages locally.

Who it is forA developer who wants to audit the Linux packaging layer, change the electron-builder setup, or produce packages on their own machine.

The problemDownloaded binaries are unsigned, so some users want to build from the source they can read.

The outcomeLocal x64 or arm64 Linux desktop packages are produced from the fork's packaging scripts.

What you need first

  • A Linux machine on x64 or arm64, such as Ubuntu, Debian, Raspberry Pi 5, or an ARM server
  • Internet access to download packages from the repository's Releases page
  • sudo rights to install the .deb package or libfuse2
  • For building from source: Node.js 24+, pnpm, and libfuse2 on the build host

Steps

  1. Clone the repository with git clone https://github.com/Zhou-Yujing114514/deepseek-harness-linux.git and change into it with cd deepseek-harness-linux.
  2. Install dependencies with pnpm install.
  3. Copy the example settings with cp apps/desktop/.env.linux.example apps/desktop/.env.linux and fill in the release settings you need.
  4. Build the x64 package with pnpm --dir apps/desktop run package:linux:x64, or the arm64 package with pnpm --dir apps/desktop run package:linux:arm64.

Prompt for your agent

For the repo Zhou-Yujing114514/deepseek-harness-linux, clone it into <target-folder>, run `pnpm install`, and build with `pnpm --dir apps/desktop run package:linux:x64`. Report which package files were created under the build output and their names. Verify that the build exits with status 0 and that the files include the .AppImage, .deb, and .tar.gz types.

Caveat. The build needs Node.js 24+ and libfuse2 on the host, and the README does not say where the output files are written, so check the build log for the output path.

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