RepoPilot

deepseek-ai / deepseek-harness

Search deepseek-ai/deepseek-harness

GitHub

Code

How deepseek-ai/deepseek-harness is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new plugin/skill

  • Create a new package under packages/[feature-name]/ following the monorepo structure
  • Implement plugin class extending core plugin interfaces; expose via packages/core abstractions
  • Register plugin capabilities in MCP protocol if exposing tools to LLM
  • Add plugin to host initialization configuration in packages/host

Add LLM provider support

  • Implement provider adapter in packages/llm following abstraction interfaces
  • Integrate with credential storage for API keys and auth tokens

Add a new tool/environment capability

  • Choose capability type: browser (packages/browser-use), computer (packages/computer-use), terminal (packages/terminal), or custom
  • Implement environment plugin and expose actions as MCP tools
  • If requiring isolation, configure sandbox constraints in packages/sandbox
  • Register tool availability in host configuration

Add a Web UI component or page

  • Create component in apps/web following React/Vue patterns (check existing structure)
  • Connect to session/context via packages/session and packages/context hooks
  • Communicate with host via API layer in packages/api if needed

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

  • Branch points10 per file on average
  • Code issues0 errors, 2 warnings
  • Largest file262 lines
  • Hotspot load0 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions · GitLab CI25 workflows
  • Tests3,557 test filesPytest · Jest/Vitest · 1.1 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: apps/cli/tests · apps/cli/tests/fixtures · .github/review-ownership

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.