Who it is forA contributor or agent that plans to change the DSH Usage code and needs a safe baseline first.
The problemChanges to balance schemes, token folding, or the server boundary can break silently without a baseline test run.
The outcomeAll syntax checks and offline tests pass on a clean checkout, giving a known starting point before edits.
What you need first
- DeepSeek Harness host, version 0.2.0-rc.2 for v0.3.1 of this plugin, with the dsh CLI installed
- An API key for each provider you want to query, configured through Harness credentials (for example DEEPSEEK_API_KEY)
- Node.js and npm only if you plan to run the offline tests or develop the plugin
Steps
- Clone the repository with
git clone https://github.com/Aisland-SJL/dsh-usage.gitand change into the folder. (inferred, check the README) - Run
npm installto add react, react-dom, and jsdom for offline tests only. - Run
npm run checkto run syntax checks for every module and script. - Run
npm testto run the 112 offline tests. - Run
npm run test:packageto check the runtime dependency and client inject contract.
Prompt for your agent
In the repo Aisland-SJL/dsh-usage, run npm install, npm run check, and npm test, then report the pass count out of 112. Verify that no test touched the real ~/.dsh directory, as the README says the tests redirect DSH_HOME to a temp dir.
Caveat. The README says the tests are offline and do not establish acceptance for every account, historical session, or Desktop feature.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Aisland-SJL/dsh-usage and "Run the offline test suite before editing the plugin"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer