dpskh/dsh-checkpoint
Mark an exploration start in the session; pairs with rewind to fold the exploration out of context.
@dpskh/tool-checkpoint provides ctx.checkpoint — a service that durably records a checkpoint mark in the plugin-owned storage domain, keyed by session id — plus the model-facing checkpoint tool over it. The marker records the conversation position an exploration starts from; the sibling @dpskh/tool-rewind plugin folds everything after the marker into an auto-generated report, keeping the noisy middle (reads, searches, experiments) out of model-visible context while the durable log retains the full exploration. The marker itself never enters model-visible history or the session log, and the fixed tool schema keeps the request prefix stable for KV-cache reuse.
Install
git clone https://github.com/dpskh/dsh-checkpoint && pnpm add /path/to/dsh-checkpointnpm name @dpskh/tool-checkpoint is not on the registry (404 verified 2026-08-31) — the README documents a profile patch-row install: add a row - id: tool-checkpoint / name: '@dpskh/tool-checkpoint' to the profile's cordis.patch.yml (pair with @dpskh/tool-rewind from dpskh/dsh-rewind for the full workflow). Clone the repo and point the row at the local package.
Compatibility
DSH profile; pairs with @dpskh/tool-rewind; prefix-stable KV-cache design; MIT.
Details
- Repo: dpskh/dsh-checkpoint
- Category: Agent Capabilities
- Stars: 2
- Version: repo dpskh/dsh-checkpoint (@dpskh/tool-checkpoint)
- Last push: 2026-08-21
- First seen: 2026-08-07
Recent updates
ctx.checkpoint service + checkpoint tool; durable storage keyed by session; mark-then-rewind workflow; marker never enters history; prefix-stable schema.
FAQ
- What does a checkpoint actually do?
- It durably records the conversation position where an exploration starts; paired with @dpskh/tool-rewind, everything after the mark folds into an auto-generated report so the noisy middle stays out of context.
- Is a marker without rewind harmful?
- No — it is inert: it costs nothing but leaves the exploration in context; the workflow depends on the model pairing mark and rewind.
- Why is the tool schema fixed?
- Prefix-stability: the fixed schema means markers (storage records, not session events) never alter the request prefix, preserving KV-cache reuse.
Alternatives
dongsheng123132/dsh-lineage · 030611/dsh-context-provenance · LeslieWylie/dsh-ops-kit