sev7een7/dsh-sieve is a plugin for DeepSeek Harness (DSH) that tidies up tool outputs and past conversation records in order to reduce the tokens that the agent has to resend at every step. The repository description states that the payload became 36% smaller in offline replay. The commit d575077 dated October 22, 2026 raises both packages, dsh-sieve and dsh-sieve-web, to 0.3.0 and aligns them with DSH 0.2.1-rc.2. The scope of the change is 14 files and 1,843 lines (1,019 lines added, 824 lines deleted).
The centerpiece is compatibility alignment. The DSH dependency was raised to 0.2.1-rc.2, Cordis was matched to 4.0.5, Schemastery to 3.18.5, and zod and dsh-storage-domain to 4.4.3, and dsh-working-directory is now required as a new peer dependency. The client platform module table was also aligned with the rc.2 shell, and the release waiting-period exception that applied only to alpha versions was removed. A row for 0.3.0 → 0.2.1-rc.2 was added to the README compatibility table, and the install command and release address that had pointed to `sieve` were replaced with `dsh-sieve`.
Behavioral changes came in as well. One is that the basis for clearing past results is now interpreted as the working directory in which each read was executed. It is computed by folding working-directory and change over the path (projection state version 4), which means the basis for path interpretation is no longer a single one but is now per working directory. The other is that the "most recent 4 (keepRecent)" criterion changed from tool results to steps, and when a forgotten file is read again it is no longer deleted again on the basis of age; instead that re-read amount is deducted from the displayed savings.
That said, DSH 0.2.1-rc.2 is a release candidate (rc). Since this is a change made to match a state in which the target platform itself is not yet settled, this commit alone cannot tell whether 0.3.0 will run stably together with the final DSH. The 36% in the repository description is also based on offline replay, and what is actually forgotten and how much depends on the verdict of the judging model. The confirmed facts are the MIT license, the condition of Node.js `^22.19.0 || >=24.0.0`, and the 265 tests passing as shown by the README badge. Anyone using DSH should first check whether this rc dependency fits their own environment.