ToolJovia
Text

Hash-guarded Selective Text Changes

Inspect exact line-change hunks and apply only selected content-derived IDs against a guarded base and proposal.

✓ Browser-local processing

Loading tool…

How to use Hash-guarded Selective Text Changes

Accept a reviewed subset of proposed text edits while retaining unselected original content. An inspect manifest exposes source hashes and exact removed/added text; apply mode refuses stale hashes or unknown hunk identities before producing a separate file.

  1. Enter original base text, proposed text, apply manifest json (from inspect result).
  2. Choose the settings for hash-guarded selective text changes, then run the tool.
  3. Review the result and any limitations before copying or downloading it.

Good to know

  • 20,000 characters and 500 LF-separated lines per source, 1,000 diff edits, a 250 ms diff budget and an isolated browser worker with a 2-second compute deadline.
  • Exact LF-token comparisons preserve CR characters and final-newline state. Offsets are labeled UTF-16 code units. Only two-source selective acceptance is supported; there is no three-way merge, fuzzy patching or automatic conflict choice.
  • Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.

Common questions

Can an old manifest be applied after either text changes?

No. Both SHA-256 source hashes must match, and every selected content-derived hunk ID must exist in that exact comparison. A stale or unknown choice yields no changed-file download.

Is this input sent to a server?

No. The application processes this input inside your browser tab and does not save it to persistent storage.

Keep going with related tools

All text →