DeepSeek Harness plugin

dsh-file-changes

Per-turn file-change panel: lists created/modified files at the end of every answer, shows their diffs, and reveals them in the OS file manager

Jump to install

Source facts

Repository
mixin-ai/dsh-file-changes
Latest update
Aug 14, 2026
Category
Plugin Markets & Managers
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/mixin-ai/dsh-file-changes
Plugin: dsh-file-changes
Author: mixin-ai

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

dsh-file-changes

A DeepSeek Harness Web plugin that shows a file-change panel at the end of every answer. When a turn creates or modifies files, the panel lists each one under the closing message with three actions:

  • Open — click the file name to open it with the OS default application;
  • View diff — a modal renders the turn's actual applied changes (whole-file

content for new files) using the harness DiffBlock primitive;

  • Reveal — locate and select the file in the OS file manager

(macOS open -R, Windows explorer /select,, desktop Linux opens the containing directory). The action appears only on loopback access with a native opener available.

The panel complements the built-in "Produced" row: it adds created/modified badges, per-file diffs, and per-file filesystem reveal.

Install

# from GitHub
dsh plugin --profile web add git+https://github.com/mixin-ai/dsh-file-changes

# from a local checkout
dsh plugin --profile web add link:/path/to/dsh-file-changes

Restart dsh web, then refresh the browser page.

How it works

  • Native mode — the client half registers a conversation definition (like

@deepseek-ai/dsh-client-ui-deliverables) that accumulates successful mutation tool calls from their presentation views (card: 'diff' hunks, or generic kind: 'edit' locations) into turn-scoped data published under the fileChanges key, and renders it through the chat view's conversation.chat.turnTail slot chain.

  • Code Mode (run_code) — nested dispatches carry no presentation views

on the wire, so the host half listens to tools/execute / tools/result for executions with a parent (Code Mode sub-calls), rebuilds change records from the write / edit / str_replace_editor arguments, and serves them over /api/file-changes/changes. The panel merges both sources, deduplicated by path.

  • RevealPOST /api/file-changes/reveal validates a JSON payload,

loopback origin, and an absolute existing path before handing it to the platform opener.

Structure

FileRole
lib/index.jsHost half: nested-dispatch tap + the two HTTP routes
lib/client.jsBrowser bundle: turn accumulator + panel/diff/reveal UI
cordis.patch.ymlBundle patch mounting the dual-half row
smoke.test.mjs / client.test.mjsHost and client logic tests

Run the tests with:

node smoke.test.mjs && node client.test.mjs

Limitations

  • Files created indirectly by terminal commands (e.g. bash) are not

detected — the same vocabulary limit as the official produced-files row.

  • Host-side Code Mode records live in memory (2-hour / 2000-per-session ring);

a server restart clears them.

  • The reveal endpoint trusts loopback same-origin JSON requests only.

License

MIT