dsh-wallpaper-engine
把本机 Wallpaper Engine 的壁纸搬进 DSH 网页界面：场景壁纸由内置 MIT 开源引擎 WebWallGL 实时 WebGL 渲染（粒子 / puppet 骨骼 / SceneScript / 音频反应 / 鼠标交互），失败自动降级内嵌 MP4 与场景静态帧；Web 壁纸严格沙箱 + WE API；iOS 风格液态玻璃 UI 高度自定义，遮挡暂停省电、ffmpeg 帧率上限转码、系统音频频谱与 Now Playing、自定义上传与自动轮播；设置存宿主端，对 agent 零 token 开销。Windows / macOS / Linux 三平台原生（同一个包、同一条命令）。
Runssource: GitHubJavaScriptMITcommit 7ba44b2424e5
JavaScript, MIT licensed. The project labels itself: deepseek harness, dsh plugin, dsh plugin market, dsh plugins, liquid glass, theme, wallpaper and wallpaper engine.
dsh-wallpaper-engine runs. An Argusic agent installed it in 8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
In this container the plugin installs into a web DSH profile (exit 0, 8 link packages registered), the live DSH web harness boots and serves /wallpaper-engine/inventory (200 JSON), /wallpaper-engine/diag (204) and /wallpaper-engine/diag-log (200 with the probe marker), and the 92-step verify suite (109 node:test pass) plus 6-step smoke suite pass using local Node 24/22, pnpm 9.15.9, dsh 0.1.7-rc.2 and a --no-sandbox...
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.
- No system Chromium; the container lacks user namespaces so Chromium needs --no-sandbox4 minutes
- System Node was v18.19.1 (plugin requires >=22.12) and the shipped dsh 0.1.7-rc.2 CLI silently no-ops on Node 22.14 because its bin.js gate is import.meta.main (undefined before Node 24); dsh --version printed empty3 minutes
- node scripts/install-source.mjs failed at 'dsh plugin add' with ERR_PNPM_ADDING_TO_ROOT because the profile pnpm workspace declares packages: ['.']; neither the --ignore-workspace-root-check flag nor the workspace yaml key took effect through the dsh plugin manager2 minutes
- Full verify chain hung under Node 24 at test/verify-upload-store.mjs after printing ALL UPLOAD-STORE CHECKS PASSED (35)1 minute
- dsh web exited right after printing the token URL when it tried to open the default browser1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 72 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- dsh --version printed 0.1.7-rc.2; node scripts/install-source.mjs --profile web --dsh-home /tmp/hm-fresh3 --app-closed exited 0 printing 'Source deployment verified: main package + 7 subpackages'; node test/compat-harness-live.mjs --fresh --channel link exited 0 (COMPAT LIVE PASSED - 13 criteria) and --channel tarball exited 0 (COMPAT LIVE PASSED - 25 criteria); WE_TEST_BROWSER=/tmp/run-glass-browser.sh npm run verify exited 0 ('verify 全部 92 步执行完毕', node:test 109 pass / 0 fail, 183 check lines, browser step 629 PASS / 0 FAIL); WE_TEST_BROWSER=/tmp/run-glass-browser.sh npm run smoke exited 0 ('smoke 全部 6 步执行完毕'); dsh web --no-open stayed up on http://127.0.0.1:3080/?token=... and curl returned 200 JSON on /wallpaper-engine/inventory, 204 on /wallpaper-engine/diag?msg=argusic-probe, 200 on /wallpaper-engine/diag-log containing that probe
- Model tokens used
- 6,445,508
- Exact commit tested
- 7ba44b2424e5
- 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.
succeeded in 1215ms: 08:57:03 === install-source runs (3 attempts, all exited 0 after wrapper) === --- fresh3 (with pnpm wrapper) --- Done in 237ms using pnpm v9.15.9 Source deployment verified: main package + 7 subpackages. Restart the target DSH host. --- wrapper file present --- -rwxrwxr-x 1 runner runner 349 Oct 30 08:29 /tmp/pnpm-wrap/pnpm --- packages/fonts build subpackage path exists --- /work/repo/packages/fonts/lib/client.fonts.js tokens used 6,445,508
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 8 minutes.
- 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.
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 8 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)
deepseek-harnessdsh-plugindsh-plugin-marketdsh-pluginsliquid-glassthemewallpaperwallpaper-enginewebgl
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dsh-wallpaper-engine)Questions
- Does dsh-wallpaper-engine run?
- Yes. dsh-wallpaper-engine runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test dsh-wallpaper-engine?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ba44b2424e5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test dsh-wallpaper-engine?
- The run that produced this verdict cost $1.37: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does dsh-wallpaper-engine take to install?
- 8 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-wallpaper-engine need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dsh-wallpaper-engine?
- 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.
- Where is the evidence for dsh-wallpaper-engine?
- 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.