BOWLUNA/dsh-zcode-breaker

English | 中文

A rapid-refill circuit breaker for DeepSeek Harness automatic compaction: it stops the futile compact-refill-compact loop and tells the user which oversized read or tool output caused it. Derived from the ZCode implementation of the same idea.

dsh plugin --profile web add dsh-zcode-breaker

Node: the harness this plugin hooks does not install on node 20 — npm install @deepseek-ai/dsh brings in 10 packages and no dsh binary there, against 488 on node 24. package.json still declares >=20; the badge says what has been measured. Raising the declared floor is tracked as an open decision rather than quietly changed here.

What it takes from ZCode, and where it goes further

Every row is meant to be checkable. The middle column names a file and line in the ZCode source — and those citations are not typed by hand and trusted: verify-zcode-citations.mjs in the control workspace resolves each one against a checkout and prints the line it found. The last column names a command you can run right now; where there is nothing to claim, the row says so instead of inventing a difference.

Two of these paths were wrong until 2026-09-22: they read core/src/compact/turn-loop-state.ts and core/src/compact/runtime/methods/compact.ts, copied from a design note rather than from the source. The files are at packages/core/src/runtime/methods/. The guard could not catch it, because a path with no line number is not a citation it looks at — which is why the middle column now carries line numbers.

ZCode has	This plugin takes	Where this goes further	Evidence
The rapid-refill state machine — consecutiveRapidRefills, toolTurnsSinceCompact, shouldBlock, computed in zcode/apps/zcode-cli/packages/core/src/runtime/methods/turn-loop-state.ts:158	The same three pieces of state	A tool turn is read out of DSH's durable session log — one assistant message carrying at least one tool call — instead of a counter inside ZCode's own turn loop. That is the same unit the compaction seam uses when it reasons about surface balance, so it is measured rather than guessed	node --test test/tracker.test.js — "a healthy gap never trips the breaker, however long the run"
The refusal decision — shouldBlock: consecutiveRapidRefills >= MAX_CONSECUTIVE_RAPID_REFILLS (…/turn-loop-state.ts:165), acted on by if (context.rapidRefill.shouldBlock) (…/runtime/methods/compact.ts:230)	The same refusal, before the summarization call runs	The refusal latches, and it happens before the summarization rather than after: the model call is never spent, and a tripped session stays tripped until it is re-armed	node --test test/tracker.test.js — "the trip happens before the futile compaction, not after it", "once tripped, every later attempt stays refused"
The thresholds as module constants — RAPID_REFILL_TOOL_TURN_THRESHOLD = 3 and MAX_CONSECUTIVE_RAPID_REFILLS = 3 (…/turn-loop-state.ts:21)	The same two thresholds: toolTurnThreshold and maxConsecutiveRapidRefills	They are row configuration, not compile-time constants, so a profile row and a preset row can differ — and the engine prints the values it actually got when it mounts	node tools/boot-check.mjs --port 32100 prints compaction-breaker armed: rapid below 7 tool turns, trip at 3 in a row for a row configured with 7, which the defaults would not produce
The stop message is a string the CLI prints — Autocompact stopped because the context refilled within fewer than … tool turns (…/runtime/helpers/model-errors.ts:52), with reason: "compact_rapid_refill_breaker" (:57)	A prompt section injected while tripped, plus /compaction-breaker status|reset	DSH's host catches errors thrown from the automatic compaction path and continues the turn. The same throw would leave the person with compaction silently switched off and nothing explaining it; the injected section is what makes the stop visible	node --test test/engine.test.js — "the trip registers exactly one prompt section" (name compaction-breaker:tripped), "the /compaction-breaker command reports state and resets on request"
microcompact.ts — clears whole old tool results, keeps the most recent five (…/packages/core/src/compact/microcompact.ts:14)	Not taken	Not yet proven. DSH ships a different, deterministic pruner; this plugin deliberately does not reimplement ZCode's, and claims no advantage over it	—
The breaker hangs off ZCode's own turn loop	It hangs off DSH's agent/pre-step step-pressure path, replacing one row of ctx.compaction	The mechanism is not tied to an external CLI's notion of a turn, and it installs as a one-row replacement of a single-slot service	node tools/boot-check.mjs --port 32100 — assertion B reads the row name out of cordis.patch.yml; docs/MEASUREMENTS.md records trigger=pressure arriving from a real session

Reproducing the comparison

git clone https://github.com/BOWLUNA/dsh-zcode-breaker && cd dsh-zcode-breaker
npm install --no-audit --no-fund @deepseek-ai/dsh@0.1.6-alpha.2   # the harness this plugin hooks
node --test test/tracker.test.js     # the state machine and the refusal, including the trip ordering
node --test test/engine.test.js      # the wrapper: delegation, the prompt section, the command
node tools/boot-check.mjs --port 32100   # the plugin really installs and really starts (four assertions)

node --test needs no test runner and no dependencies. The first two commands are the evidence column above; the third is the only check in this repository that actually applies the plugin.

The problem, concretely

Automatic compaction has two trigger paths in @deepseek-ai/dsh-compaction-basic:

Trigger	Entry point	Attempt bound
Step-boundary pressure	agent/pre-step calls compactIfNeeded(agent, "pressure")	none
Context-overflow recovery	agent/request-error calls compactIfNeeded(agent, "context-overflow")	maxOverflowRetries

The pressure path is unbounded: once measured pressure exceeds thresholdRatio, the next step compacts again, and every compaction is a full summarization model call. One oversized file read or tool output therefore produces a loop that burns a model call per step until the session is abandoned, and the transcript shows only this repeating line:

compaction (step pressure): shadowed N surface nodes (seqs A-B, ~T tokens)

What it does

It extends BasicCompactionEngine and wraps exactly one method, compactIfNeeded:

• State is per session, so sessions cannot pollute each other.
• A tool turn is read from the durable session log: one assistant message carrying at least one tool call. That is the unit the compaction seam itself uses when it reasons about surface balance, rather than a guessed step count.
• A compaction requested fewer than toolTurnThreshold tool turns after the previous one counts as a rapid refill.
• At maxConsecutiveRapidRefills in a row the attempt is refused before it runs, so the summarization call is never spent.
• A refusal latches and throws a CompactionRapidRefillError carrying actionable advice.
• It also injects one prompt section while tripped, because the host catches errors from compactIfNeeded and continues the turn: a thrown error alone would leave the person with no explanation.
• The command /compaction-breaker reports the state and can re-arm it.

Everything else stays the base engine's: trigger policy, retention, surface mutation, tool-pairing safety and summarization.

Two planes, and why both matter

compaction-basic exists twice in a stock harness: once as a host-plane row in @deepseek-ai/dsh-base, and once inside the agent preset's compaction group, which is declared isolate: { compaction: true, toolResultPruner: true }. An agent session resolves ctx.compaction inside that isolated realm, while a session that joins no preset resolves the host row. That is why a profile patch alone cannot change an agent's compaction, and why the preset row in the second half of this section exists.

The seam is single-slot: a second provider in the same isolate scope makes ctx.provide() throw, and ctx.reflect.set() accepts writes only from the owning fiber. Each plane is therefore covered by replacing its row, never by shadowing it.

Plane	Who it serves	How this package covers it
Host	sessions that join no agent preset	automatically, through the bundle patch the installer mounts
Agent realm	every ordinary session	one row replaced inside your agent preset, because no profile patch can reach a realm

Which harness versions this supports, and why it stops where it does

>=0.1.5-rc.2 <0.1.6-0 || >=0.1.6-alpha.1 <0.1.7-0

0.1.7 is not supported, and the range says so. That is measured, not assumed. On a real 0.1.7-alpha.2 instance (dsh017 in this project's lab):

	0.1.6-alpha.2	0.1.7-alpha.2
dsh plugin add	exit 0	exit 0
--dump-config	exit 0 · 576 lines · stderr 0 B	exit 0 · 1237 lines · stderr 0 B
real boot on a port	answering at t=1500 ms · stderr 0 B	answering at t=2000 ms · stderr 0 B
host plane serves this engine	yes	yes — a probe read ctx.get("compaction") as BreakerCompactionEngine with compactIfNeeded a function
preset plane	a preset in <DSH_HOME>/.agent-presets/ is discovered	no — list() returned [] with breaker-trip seeded

0.1.7 replaced preset discovery with a declarative registry (dsh-agent-preset-registry, self-described as "Declarative Agent preset registry and profile-backed editing"), and the registry does not scan directories. The host half of this plugin works there; the half the README above tells you to set up does not. Advertising "supports 0.1.7" on the strength of the host half would be a half-truth, so the range excludes it — including the 0.1.7 release, which a range written as ... <0.2.0-0 would still accept. tools/verify-version-consistency.mjs now fails the build if the declared range covers a version on its measured-unsupported list, which is how this gap was found.

Install

dsh plugin --profile web add dsh-zcode-breaker

The install mounts cordis.patch.yml, which disables the host-plane compaction-basic row and puts this engine in its place. Replacing rather than wrapping is forced by the single slot.

Then, for agent sessions, replace the row inside your preset's compaction group in agent.cordis.yml:

- id: compaction
  name: cordis:group
  group: true
  isolate:
    compaction: true
    toolResultPruner: true
  config:
    - id: compaction-breaker
      name: 'dsh-zcode-breaker'
      config:
        toolTurnThreshold: 2
        maxConsecutiveRapidRefills: 3
    - id: command-compact
      name: '@deepseek-ai/dsh-command-compact'

Copy the preset into your user preset directory rather than editing the shipped one, or a harness upgrade will overwrite the edit.

Configuration

Every base-engine key survives, re-declared on the subclass so it is neither rejected by the base engine's strict validator nor lost:

Key	Default	Meaning
thresholdRatio	0.8	pressure ratio that triggers compaction
retainRatio	0.16	retained tail ratio after compaction
retainTokens	none	absolute token retention instead of the ratio
summarizationProvider	empty	route used for summaries
summarizationModel	empty	model used for summaries
maxTokens	8192	summary output cap
compactionRetries	1	retries after a failed summary
maxOverflowRetries	1	overflow-recovery retries
modelPolicies	none	per provider and model overrides of the keys above
auto	true	automatic compaction master switch

Added by this plugin:

Key	Default	Meaning
toolTurnThreshold	2	a gap under this many tool turns is rapid; exactly the threshold is not
maxConsecutiveRapidRefills	3	refuse on the Nth consecutive rapid refill
announceInPrompt	true	inject the advisory prompt section once tripped

That is 13 config keys in total, and this file declares compatibility with dsh >=0.1.5-rc.2 <0.1.6-0 || >=0.1.6-alpha.1 <0.1.7-0.

Surfaces

Surface	What it shows
Log	one warn line naming the consecutive count, the threshold and the last gap
/compaction-breaker	a state report; /compaction-breaker reset re-arms
Prompt section	injected while tripped, instructing the model to relay the situation

Semantics — three deliberate decisions

1. A refusal latches. A refused attempt never commits, so without latching the breaker would release itself once the gap passed the threshold, blocking twice and allowing once. The latch is what makes this a stop rather than a slowdown.
2. Two ways out exist: the reset subcommand, or a successful manual /compact. A person deliberately compacting is new information and should not be refused because of what the automatic path did earlier.
3. Reset does not zero the tool-turn clock. It is the session's monotonic clock, and zeroing it would make every later gap look healthy. Only the rapid counter, the last compaction mark, the latch and the refused-attempt count are cleared.

A trip is not a global disable: the session keeps working, only automatic compaction is off for it.

Compatibility and known limits

• It is mutually exclusive with other compaction engines. Several backends occupy the same ctx.compaction slot, and none of them can be mounted alongside this engine. That is a limitation of the seam rather than a choice made here.
• The host-plane row is untouched, so sessions that do not compose a preset are unaffected.
• Base defaults are inherited, since the base engine's own schema carries no defaults and its resolver supplies them. A future base-engine key therefore needs re-declaring here to remain configurable.
• State lives in module-level WeakMaps rather than private class fields. That is deliberate: the object a realm hands out as ctx.compaction is not reliably the one whose private initializers ran, and a private-field read would throw inside the compaction path where the host swallows it.
• The model-driven end-to-end acceptance has not been run. Everything up to and including the engine serving ctx.compaction inside a real realm is verified; see docs/MEASUREMENTS.md.

Composing with another backend

The policy core is exported so another backend can adopt it in roughly twenty lines:

import { RapidRefillTracker } from 'dsh-zcode-breaker/tracker';

const tracker = new RapidRefillTracker({ toolTurnThreshold: 2, maxConsecutiveRapidRefills: 3 });
tracker.noteToolTurn();
const gate = tracker.gate();
if (gate.blocked) throw new Error('rapid refill loop');
const result = await myEngine.compact();
if (result !== null) tracker.commitCompaction(gate.projectedConsecutiveRapidRefills);

Tests

npm test

19 tests in 2 suites, with no services, no model and no session: the policy core in test/tracker.test.js and the engine wiring in test/engine.test.js. The wiring suite needs the peer packages resolvable and skips rather than fails where they are missing.

Roadmap

• Run the model-driven acceptance: build a refill loop in a real session and watch the breaker trip.
• Choose the base class at runtime, so the breaker composes with whichever backend a user prefers.
• Offer the policy core upstream to @deepseek-ai/dsh-compaction-basic.

License

MIT