Introduction

DSH’s philosophy is “everything is a plugin”. When using profiles and plugin manifests in practice, environment configurations may change over time; troubleshooting “what changed in the environment recently” becomes troublesome without a clear timeline.

dsh-config-watch is a DeepSeek Harness plugin maintained by Equinox7379, used to record the history of environment configuration changes. It takes a snapshot at every service startup, compares it with the previous snapshot, writes the differences to a change log, and provides a read-only history for future queries.

What is this

One-sentence positioning: DeepSeek Harness plugin: records history of environment configuration changes.

  • Plugin name: dsh-config-watch
  • Maintainer: Equinox7379
  • License: MIT
  • Problem solved: Provides a timeline of when the environment was changed.
  • Snapshot method: Only saves hashes and filenames, does not copy file content.

Core Features

The verified capabilities are as follows:

  • Records history of environment configuration changes.
  • Takes snapshots of profile key files and the plugin manifest at every service startup.
  • Compares with the previous snapshot and writes differences to the change log.
  • Provides the config_changes tool.
  • Supports the limit parameter, defaulting to 20, returning the most recent N entries within a maximum of 200.
  • Zero dependencies, no custom session events, no HTTP routes.

Installation and Activation

First prepare the local path for the plugin, then use the following command to install. The command uses --profile web and the local path link:/path/to/dsh-config-watch. After installation, dsh web needs to be restarted.

dsh plugin --profile web add link:/path/to/dsh-config-watch
# Restart dsh web

The verified facts do not provide a command to install directly from the GitHub repository. package.json declares dsh.bundle.patch as ./cordis.patch.yml, but the content of this file was not fetched, so specific patch configuration cannot be confirmed.

Typical Usage

After enabling the plugin, use the config_changes tool to query history. The limit parameter defaults to 20, returning the most recent N entries within a maximum of 200.

For example, when asking “what changed in the environment recently”, it can return entries and total. The README example is as follows:

{ "entries": [ { "at": "2026-08-14T09:47:00Z",
    "changes": [ { "kind": "plugin-added", "target": "dsh-modsearch", "detail": "2026-08-14T09:40:12Z" } ] } ],
  "total": 37 }

In this example, entries is a list of change records, and total is the total number of historical entries. In changes, you can see that kind is plugin-added and target is dsh-modsearch.

Data Storage and Reliability

  • Data is only written to ~/.dsh/config-watch/.
  • Data includes history.jsonl and last-snapshot.json; history.jsonl has a rotation limit of 200 entries.
  • Snapshots only save hashes and file names, not file content.
  • Snapshot failures are only logged and do not affect service startup.
  • Zero dependencies, no custom session events, no HTTP routes.

Use Cases and Notes

Suitable for scenarios where you need to troubleshoot DSH environment configuration, changes to key files in profiles, and plugin manifests. It provides a change history based on snapshot comparison at startup, not saving the full file content.

It is recommended to check the source code and license before installation. The plugin runs with the privileges of the current dsh process; before installation, you should confirm that the local path, source, and runtime environment meet the requirements.

The DSH Community Directory is an independent site and has no official affiliation with DeepSeek / Huanfuan.

Links

  • Plugin Directory Page (Plugin Tracer): https://www.skillhub.cn/plugins/Equinox7379/dsh-config-watch
  • GitHub Repository: https://github.com/Equinox7379/dsh-config-watch