Preface¶

When debugging Agent behavior in DSH, it’s often useful to confirm what changed between two adjacent requests: whether the provider/model changed, whether the system changed, whether the tools directory changed, or whether there are differences in the source categories of skills or AGENTS.
However, directly reading the request body can easily expose sensitive content such as prompt text, message content, tool schemas, and raw paths.

dsh-context-provenance is a DSH plugin designed for this scenario: it does not return these raw contents, but instead marks the evidence of adjacent requests as Observed, Estimated, or Unavailable, relying only on information provable through public runtime interfaces.

What This Is¶

dsh-context-provenance is an MIT-licensed plugin maintained by 030611. It is a community-maintained project and is not an official DeepSeek project.

Its positioning is an observe-only provenance ledger, targeting public DeepSeek Harness runtime evidence.
The plugin itself is observe-only, CPU-only, and local-only. It does not perform file, network, subprocess, GPU, persistence, session, permission, tool, model-routing, or request modifications.

It retains only the most recent two observations of ordinary agent-loop requests and keeps them in memory; observation results are exposed through the existing Cordis inspect query mechanism.

Core Features¶

• Compares evidence from adjacent requests and marks fields as Observed, Estimated, or Unavailable.
• Does not return prompt text, message content, tool schemas, or raw paths.
• Retains only the most recent two observations of ordinary agent-loop requests.
• Does not perform file, network, subprocess, GPU, persistence, session, permission, tool, model-routing, or request modifications.
• Adds a Host provider ContextProvenance with method report when the official Cordis inspect service exists.
• When service, projection keys, optional fields, or incomplete skill discovery are missing, fields degrade accordingly; absence is not silently converted to zero.

The request body is synchronously reduced at the llm/stream boundary. System text, messages, tool descriptions, JSON parameter schemas, raw plugin identifiers, raw skill provider/source identifiers, and AGENTS paths or contents are not returned.

Installation and Activation¶

First, verify the DSH version and Node.js version. Plugin version 0.1.1 only supports DSH 0.1.1-rc.2, and requires Node.js ^22.19.0 || >=24.0.0.
DSH 0.1.0-rc.8 and 0.1.1-rc.1 are explicitly incompatible with this version.

Install to a specific profile:

dsh plugin --profile <profile> add dsh-context-provenance

Check the resolved configuration:

dsh --profile <profile> --dump-config

Before installation, it is recommended to verify the registry version, source tag, and release notes. Do not treat an untagged repository checkout as a release artifact.

After installation, restart DSH, then use existing inspect tools to query the Host provider ContextProvenance method report. If the official Cordis inspect service is not present in the environment, the plugin can still mount the observer, but there will be no query surface.

Typical Usage¶

Using the web profile as an example:

dsh plugin --profile web add dsh-context-provenance
dsh --profile web --dump-config

The commands above add the plugin bundle to the web profile and output the profile’s configuration.
Then restart DSH and query the report method of ContextProvenance through existing inspect tools.

Note: Observation data is only kept in memory for the most recent two request observations; restarting or uninstalling the plugin will lose all observations.

Applicable Scenarios and Considerations¶

This plugin is suitable for the following scenarios:

• Comparing evidence changes between adjacent requests without directly viewing the request body.
• Needing to clearly distinguish between Observed, Estimated, and Unavailable.
• Not wanting the plugin to perform additional file, network, subprocess, GPU, persistence, or request modifications.
• Needing to view public runtime information exposed by the existing Cordis inspect.

Points to note:

• This plugin is not a complete context provenance graph and cannot explain all behavioral differences.
• It only retains the most recent two observations of ordinary agent-loop requests; observations are lost after restart or uninstall.
• Without the official Cordis inspect service, the query surface is unavailable.
• DSH plugins run with the permissions of the current dsh process; you should inspect source code, dependencies, licenses, and release versions before installation.

Links¶

GitHub:

https://github.com/030611/dsh-context-provenance

Community directory page (provided as a lead, unconfirmed, verify independently):

https://www.skillhub.cn/plugins/030611/dsh-context-provenance