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

How to build and run the harness from a git checkout with DeepSeek Harness

Clone the repository, install dependencies, build the artifacts, and start the Web UI from source.

Who it is forA developer who wants to read, modify, or debug the harness code instead of using the published package.

The problemThe npm launch hides the source, so changes to the harness need a local build from the repository.

The outcomeThe Web UI runs from your own build of the repository.

What you need first

  • Node.js installed
  • A terminal and a web browser
  • pnpm, if running from source
  • Git, if running from source
  • Review of the SAFETY.md safety notice before running the project

Steps

  1. Install Node.js and pnpm.
  2. Run git clone https://github.com/deepseek-ai/deepseek-harness.git and then cd deepseek-harness.
  3. Run pnpm install, then pnpm run build.
  4. Run pnpm dsh web to start the Web UI using the built artifacts.

Prompt for your agent

Clone https://github.com/deepseek-ai/deepseek-harness into <target folder>, run `pnpm install` and `pnpm run build`, then `pnpm dsh web`. Report whether the build finished without errors and the URL the Web UI is served on.

Caveat. The README says `pnpm dsh web` uses existing build artifacts without rebuilding, so run `pnpm run build` again after source changes.

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