deepseekplugins

DeepSeek Harness plugin

deepseek-harness-hashline

Hash-anchored UTF-8 file reading and atomic editing tools for DeepSeek Harness

Tools & Capabilities
Jump to install

Source facts

Repository
magian1127/deepseek-harness-hashline
Latest update
Aug 21, 2026
Category
Tools & Capabilities
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/magian1127/deepseek-harness-hashline
Plugin: deepseek-harness-hashline
Author: magian1127

Check the source files

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

File explorer4 files
README.en.mdSource · read only
README language

deepseek-harness-hashline

中文 · English

> Experimental > > This plugin is still under active testing and is not recommended for production use. Use it at your own risk and validate it in an isolated workspace before enabling it on real projects. > > The API, settings, and tool behavior may change without notice.

<p align="center"> <img alt="Status Experimental" src="https://img.shields.io/badge/Status-Experimental-ff6b6b"> <img alt="Version 0.1.0" src="https://img.shields.io/badge/Version-0.1.0-5965d8"> <img alt="MIT License" src="https://img.shields.io/badge/license-MIT-3b7a57"> </p>

DeepSeek Harness hash-anchored file editing plugin: provides hashline_read and hashline_edit, binding edits to the exact lines most recently read by the model through LINE:HASH anchors. This helps detect stale reads, supports multiple edits in one request, and makes file changes mechanically reliable.

In the default mode, the plugin supplements the built-in read and edit tools. New files should still use write, and simple unique literal replacements can still use the built-in edit. Use Hashline when an edit must be anchored. You can also enable Replace built-in read/edit so an agent that is allowed to edit can use Hashline semantics through the read and edit names.

Features

| Capability | Description | | --- | --- | | LINE:HASH reads | Returns LINE:HASH\|text records. The default hash is a 4-character hexadecimal SHA-256 prefix covering the complete line and its real line ending. | | Three anchored edits | set_line, replace_lines, and insert_after | | Exact replacement escape hatch | replace performs strict literal matching and requires a unique match by default. | | Atomic batch edits | Validates all anchors first, rejects overlaps, and then writes atomically. | | Version CAS protection | Uses the DSH file version to prevent concurrent changes between validation and writing. | | Text fidelity | Preserves the UTF-8 BOM, LF/CRLF style, and whether the file ends with a newline. | | Stale-anchor recovery | Returns nearby current lines and fresh anchors when an anchor is no longer valid. | | Reversible replacement | Agent-scoped built-in tool replacement is reversible and is cleaned up with the owning Cordis Fiber. |

Requirements

  • DeepSeek Harness 0.1.0-rc.7 or a compatible version, using the web profile
  • Node.js ^22.19.0 || >=24.0.0
  • The web settings card also requires DSH support for settings.register(..., { exposeToClients: true })

Installation

Replace <absolute-path> with the actual absolute path on your machine. The source checkout does not track the generated lib/ directory. Install development dependencies once, then run npm run build before the first installation and after source changes:

npm install
npm run build

Local file installation:

dsh plugin --profile web add "file:<absolute-path>/deepseek-harness-hashline"

For continuous development, install with link: directly — the runtime resolves DSH peers from the profile, so no local junction setup is required:

dsh plugin --profile web add "link:<absolute-path>/deepseek-harness-hashline"

Check the composition after installation:

dsh --profile web --dump-config

Updates

Run the installation command again to update the dependency and persistent bundle. Refresh the page after browser-side changes. During local link: development, Host files hot reload when the DSH HMR service is available; otherwise restart DSH as indicated by its logs.

Uninstallation

dsh plugin --profile web remove deepseek-harness-hashline

Uninstallation removes the persistent bundle and running entries. It does not delete DSH session data. Existing user overrides in the hashline settings namespace may remain and can be reused after a later installation.

Settings and data

DataStorage
Global enable switch, built-in read/edit replacement switch, and hash parametersThe DSH hashline settings namespace, edited under Settings > Plugins > Plugin configuration

The plugin does not register capabilities beyond its model tools, upload data, or maintain independent data files. The client only contributes a configuration card to the existing settings.plugin.item slot and uses DSH settingsScope to read and write the same Host namespace.

FAQ

How is this different from the built-in read and edit? The built-in tools operate on line numbers and text. Hashline binds an edit to the hash anchor of the exact content most recently read, detects stale reads, and handles multiple edits as one atomic request.

Can a short hash collide? A short hash has a theoretical collision probability. The default 4 hexadecimal characters provide a 16-bit check and are combined with the line number and file-level version CAS. Increase hashLength for higher-risk deployments.

How does Replace built-in read/edit work? When enabled, an allowed agent sees read and edit using Hashline anchors, while hashline_read and hashline_edit are hidden. The original tools are restored when the setting is disabled. Replacement is installed only when the agent already has access to read, edit, hashline_read, and hashline_edit, so it cannot bypass visibility restrictions.

Development documentation

  • [Usage guide](docs/usage.md): tool parameters, anchor format, edit variants, and the safety model
  • [Design notes](docs/design.md): tool boundaries, anchors, text model, DSH integration, and package shape
  • [Development guide](docs/development.md): local development installation, HMR, testing, and verification

License

[MIT](LICENSE)

Back to searchOpen GitHub repository

More related plugins

View category