A fused tool call once cost a whole turn: the provider streamed two JSON objects into one call index, the adapter threw MALFORMED_RESPONSE, and the turn ended.
dsh-remedy is a patch set I built for that and the neighbouring failures on DeepSeek Harness's seams. It runs as a resident plugin on llm/stream. It splits a fused call only when every fragment can be proven to parse on its own; otherwise it rethrows the provider's failure. A chunk the wrapper cannot read is passed through rather than turned into a new exception.
There is also an offline half. scan reads this host's session logs and reports fused calls, truncations and turns that ended without an answer. explain names which patch covers a failure class, without pretending an unread profile is "off".
Measured on this tree: 54 registered patches, 451 tests, six gates, and a cold install from the registry printing OK 8 fixture(s). npm latest is 0.4.20 on both packages. Those are build and host readings, not an audience estimate.
Three boundaries: it does not patch app.asar, it is not a plugin market, and macOS is only a CI job here. External bug reports stay leads until the shape is reproduced locally.
Repo: https://github.com/jjjjjjjjnnjnn/dsh-remedy
What do you think about "rethrow rather than fake a fix" as the default for a repair layer?
Top comments (0)