dsh-config-manager
DeepSeek Harness (DSH) backup & restore plugin, export, import, migrate and sync your complete DSH configuration, plugins, MCP servers, skills and workspace. One-click migration to another machine.
Runssource: GitHubTypeScriptMITcommit 5bca520674d1
TypeScript, MIT licensed. The project labels itself: backup, cli, config manager, configuration, cordis, deepseek, deepseek harness and dsh.
dsh-config-manager runs. An Argusic agent installed it in 4 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The DSH Config Manager plugin builds successfully from source with Node.js v22.19.0, passes 5507 of 5520 tests (99.8%), all 12 smoke tests pass, and the CLI binary reports version v0.6.0 with all subcommands.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System Node.js v18.19.1 too old (requires ^22.19.0 || >=24.0.0)2 minutes
- pnpm install --ignore-scripts skipped optional native binding @rolldown/binding-linux-x64-gnu needed by tsdown1 minute
- tsdown required unrun package not in dependencies1 minute
- TypeScript typecheck has known conflict TS2717 in chat-slots.ts (SessionId vs string from DSH session types), build tsconfig excludes client dir
- 2 pre-existing test failures (MC-5 retention boundary and fork-reconcile timeout)
- Install time
- 4 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm run build exited 0 (tsc + tsdown completed); node --experimental-strip-types --test src/core/smoke.test.ts all 12 passed; node --experimental-strip-types --test 'src/**/*.test.ts' 'tests/**/*.test.ts' returned # tests 5520, # pass 5507, # fail 2, # skipped 8; CLI binary at lib/cli/index.js --help printed version and commands
- Model tokens used
- 297,673
- Exact commit tested
- 5bca520674d1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/work/repo/lib/client.js.map exec /bin/sh -lc 'find /work/repo/lib -name "*.js" | wc -l && find /work/repo/lib -name "*.d.ts" | wc -l… succeeded in 0ms: 390 390 390 JS files and 390 `.d.ts` files in lib — build is complete. Here is the final report: tokens used 297,673 390 JS files and 390 `.d.ts` files in lib — build is complete. Here is the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 4 minutes, faster than the median of the 47 comparable projects Argusic has measured.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 48 backup projects Argusic has installed and timed, dsh-config-manager was the 15th fastest to reach a running state, and 31 of 48 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 4 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
backupcliconfig-managerconfigurationcordisdeepseekdeepseek-harnessdshdsh-pluginexportimportmcpmigrationpluginrestoresettingsskillssyncwebdavworkspace
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dsh-config-manager)Questions
- Does dsh-config-manager run?
- Yes. dsh-config-manager runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test dsh-config-manager?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5bca520674d1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test dsh-config-manager?
- The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does dsh-config-manager take to install?
- 4 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does dsh-config-manager need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dsh-config-manager?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does dsh-config-manager compare with the alternatives?
- Of the 48 backup projects Argusic has installed and timed, dsh-config-manager was the 15th fastest to reach a running state, and 31 of 48 reached one at all.
- Where is the evidence for dsh-config-manager?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.