Contributing to Harness Code

August 14, 2026 ยท View on GitHub

Thanks for helping make the official DeepSeek Harness Runtime easier to use from a terminal.

Before you start

  • Search existing issues and discussions before opening a duplicate.
  • Use Discussions for questions, design exploration, and broad ideas.
  • Use Issues for reproducible bugs and scoped feature requests.
  • Never include API keys, access tokens, private prompts, or sensitive workspace content.

Development setup

Requirements: Node.js 22.19 or newer and a recent npm release.

git clone https://github.com/withlovehub/harness-code.git
cd harness-code
npm install
npm run check

Useful commands:

npm run dev
npm run typecheck
npm test
npm run build
npm run smoke:runtime
npm run smoke:package

Architecture boundary

Harness Code is a terminal host for the official Harness Runtime, not a replacement agent implementation.

  • Terminal interaction belongs in src/tui/.
  • CLI parsing and non-interactive behavior belong in src/.
  • Runtime composition belongs in runtime/cordis.yml and its local control plugin.
  • Agent behavior, tools, persistence, and sandbox policy should remain in the official Harness composition whenever possible.
  • Do not add a browser server, Electron dependency, or localhost transport to the default CLI path.

Pull requests

Keep pull requests focused and explain:

  1. What changed.
  2. Why the change belongs in Harness Code rather than upstream Harness.
  3. What users will notice.
  4. Which checks were run.

Add or update tests for behavior changes. UI changes should include a screenshot when practical. Preserve upstream attribution and the independent-community-project disclaimer.

Good first contributions

Good starting points include documentation translations, terminal accessibility, command discoverability, platform verification, and narrowly scoped tests. Look for the good first issue label.

By participating, you agree to follow the Code of Conduct.