ddggkkcc/dsh-stash

dsh-stash (workspace name dsh-stash) is a hybrid plugin built specifically for DSH, named after and packaged around the DeepSeek Harness host. It packages a host-side StashService that exposes a stash remote namespace, a storage-domain persistence layer, and a one-shot follow-up channel via ctx.llm.stream, while the client side ships a shell.overlay floating UI together with text-selection capture and a selection-scope resolver which locks the menu to the conversation container via a sentinel probe plus lowest-common-ancestor walk so out-of-scope text never triggers it. The bundle manifest declares it as a bundle-manifest plugin and the project follows an SDD workflow (vision → requirements → spec → plan → implementation → tests) with docs/spec/ treated as the binding contract.

Typical usage has two scenarios. Scenario one — "stash on the fly" — lets the user highlight an unfamiliar keyword, an inspiring snippet, or anything they want to revisit from a chat reply or file read, and silently saves it into the drawer without popups, page jumps, or interruption; the focus stays on the current conversation. Scenario two — "drawer follow-up" — opens an overlay floating window on the same page where the user can pick the current selection, a single drawer entry, or multiple drawer entries, optionally merge them with the input box, and ask a follow-up question with an explicit toggle for whether the current chat context should be joined. This is targeted at heavy AI-chat users who accumulate many side questions during one session and want them parked, not lost or scattered across new tabs.

Dependencies and limits: host code is TypeScript under src/host/, built to lib/host/ by scripts/build.sh; client code is TSX under src/client/, bundled to lib/client.js by npm run build:client using tsdown, both reported zero errors. Installation is performed through the DSH super-injector HTTP API; the team verified inject → self-check (host ✓ / client ✓ / boot manifest registered) → uninstall → reinject end-to-end, with a known injector-side macOS junction-removal quirk documented in scripts/README.md. Status as of the README is M1 core follow-up chain connected on 2026-08-20 and selection-scope plus UI redesign landed 2026-08-22 using a warm-graphite × sage token set; the next step is on-device regression covering AC-1 through AC-5, real LLM follow-ups, and the context-toggle behavior, while the README leaves the license field unspecified so downstream users should confirm licensing before redistribution.