Introduction

As an agent development platform, DSH (DeepSeek Harness) often lacks contextual awareness of interface menus, fields, and business processes when it encounters complex ERP systems. Manually writing rules for every page is both cumbersome and difficult to maintain. The guomonth/dsh-erp plugin enables DSH to observe the system directly through browser interfaces and solidify the acquired knowledge locally, allowing agents to reuse those experiences.

What Is This

This is a DeepSeek Harness plugin maintained by GuoMonth. Its core purpose is to “learn your ERP” by observing the ERP’s menus, pages, fields, and business data through browser interactions, building a local knowledge graph, and ultimately exporting the experience as reusable skills.

Core Features

  • Browser Learning: Learn accessible menus, pages, fields, and business data through browser interfaces.
  • Local Construction: Save observed knowledge locally without relying on remote servers.
  • Skill Export and Import: Export the experience from the current ERP as native skills (SKILL.md) and import it into other users’ configurations.
  • Configuration and Status Checks: Configure the plugin through cordis.patch.yml and support checking erp_system_status and erp_native_status.
  • Multi-Mode Support: Supports native DSH browser usage, with optional computer-use capabilities.

Installation and Enablement

Before installing, ensure the environment meets the requirements:
* Node.js: >=24.18.0 <25
* DSH: 0.2.0-rc.2
* Desktop environment: Linux x64, requiring a graphical session and Chromium system libraries (Windows/macOS desktop support is pending)

Install the Plugin

Use npm to run the installation command:

npm exec --yes --package=pnpm@11.7.0 -- dsh plugin --profile web add @guosheng_047/dsh-erp@latest

If the environment has only Node.js installed, you can use the following command:

npm exec --yes --package=@deepseek-ai/dsh@0.2.0-rc.2 --package=pnpm@11.7.0 -- dsh plugin --profile web add @guosheng_047/dsh-erp@latest

Configuration

Stop DSH and edit the configuration file ~/.dsh/profiles/web/cordis.patch.yml (or $DSH_HOME/profiles/web/cordis.patch.yml).

Add or modify the id: erp configuration item in the file. If the file contains comments and [], replace them with the following block:

- id: erp
  config:
    system:
      url: "https://erp.example.com/app/#/login"
      name: "My ERP"
      account: "my-work-account"
      # tenant: "my-company"
      # role: "purchasing"

The url field is required. The name defaults to the hostname, and the account defaults to default. Using different account aliases can isolate knowledge, but they are not credentials.

Start DSH:

dsh --profile web

On first launch, you need to confirm the preview notification, select a workspace, and configure the model. Then request erp_system_status and erp_native_status, open the configured ERP through the native browser tools, and log in manually.

Typical Usage

  1. Mapping and Exploration
    Ask DSH to first map the accessible menus, then explore the pages, fields, and business domains. Before operations, check the saved knowledge, obtain the current observations and approval, and verify the results afterward.

  2. Skill Export
    Export the experience from this ERP as a shareable skill. Use the erp_experience_export command, which creates a SKILL.md directory containing JSON references.

  3. Skill Import
    Import skill references and knowledge into your configured ERP. Use erp_experience_import, which rebinds the knowledge to a local scope and registers native skills. Imports do not copy login credentials or original evidence.

Applicable Scenarios and Notes

  • Applicable Scenarios: Suitable when an agent needs to understand the business processes of a specific ERP system, and the ERP has no public API or API scripts are difficult to write.
  • Permissions and Security: Native browser and computer calls require separate DSH approvals. Imported experiences do not grant operational permissions; they only contain knowledge references.
  • Compatibility: Does not depend on a specific ERP vendor or API paths, but compatibility depends on the site’s interface and authentication.
  • Notes:
    • Linux x64 desktops require a graphical session and Chromium system libraries.
    • User knowledge, browser login data, and test data are not included in npm releases.
    • It does not provide an unattended transaction engine or automatic routing across multiple ERPs.
    • Imports do not copy login credentials or original evidence; they only copy knowledge and references.

Conclusion

guomonth/dsh-erp addresses the knowledge gap that DSH encounters when working with complex enterprise systems. It converts browser interactions into locally reusable knowledge assets, making it suitable for scenarios that require private, localized knowledge management. For more information, see GitHub or the SkillHub catalog.