Who it is forA maintainer or contributor who wants an AI coding agent to make a scoped change to the harness.
The problemAn agent working in an unfamiliar repository may skip project conventions, build steps, or contribution rules.
The outcomeThe agent makes a change that follows AGENTS.md, and you can check it with the build and the dev watch command.
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
- Clone the repository and run
pnpm install. - Read AGENTS.md and CONTRIBUTING.md before asking the agent to edit code.
- Ask the agent to make the change described in your task, then run
pnpm run build. - Run
pnpm run dev:webto rebuild client bundles on source edits while you check the Web UI.
Prompt for your agent
In the deepseek-harness repository, read AGENTS.md and CONTRIBUTING.md first, then make <described change> without touching unrelated files. Run `pnpm run build` and report the result and the files changed.
Caveat. The README says there will be compatibility-breaking changes, so an agent's change may need rework after upstream updates.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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