DSH-better-sidebar

开放的侧边栏底座,支持三方拓展注册新侧边栏页面。内置文件渲染编辑/终端/侧边对话/Git/子代理页面 | Open sidebar foundation, supports third-party extensions to register new sidebar pages. Built-in file rendering/editing, terminal, side chat, Git, and sub-agent pages.

Runs with mockssource: GitHubTypeScriptMITcommit 1499502bfa63

TypeScript, MIT licensed. The project labels itself: deepseek, deepseek harness, dsh, dsh better sidebar, dsh plugin and sidebar.

DSH-better-sidebar runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

dependencies install, typecheck, lint, and build all succeed; 67 unit tests pass; 18 locale files synced to 519 keys each; git identity configured

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 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
2
last tested
stars
3,969
forks
386
open issues
301
watchers
7
size
5 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . 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.

Time lost to each failure while testing DSH-better-sidebar, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18 did not satisfy pnpm 11 requirement (>=22.13); pnpm 9 used instead then Node upgraded via 'n' to v225 minutes
  • All 18 non-zh locale files missing 6 keys each (pluginAgentPersonaName, pluginAgentPersonaDesc, pluginTylinaName, pluginTylinaDesc, pluginMnemeName, pluginMnemeDesc)5 minutes
  • Japanese locale file missing pluginMnemeName and pluginMnemeDesc keys, key-set equality test failed2 minutes
  • git identity not configured, causing revert/cherry-pick tests to fail1 minute
  • market-manifest pack test very slow (288s) and plugin-meta pack test also slow; E2E tests need real DSH host
Install time
25 minutes
Cold machine to finish
77 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
pnpm test --reporter=verbose tests/locales.spec.ts tests/smoke.spec.ts tests/api-surface.spec.ts tests/market-manifest.spec.ts exit code 0, 67 tests passed; full run timeout but partial runs show 207+ passed with no failures
Model tokens used
825,793
Exact commit tested
1499502bfa63
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Installation**: Set up Node.js v22.23.3 (via `n`), installed pnpm 9.15.9, ran `pnpm install --fro…
**Issues found and fixed**:
1. **Node.js too old (v18)** — pnpm 11 required Node >=22. Installed **pnpm 9** (compatible with No…
2. **Git identity missing** — `git config --global user.name` and `user.email` were not set, causin…
3. **Japanese locale file missing 2 keys** (`pluginMnemeName`, `pluginMnemeDesc`) — `locales.spec.t…
4. **All 18 non-zh locale files missing 6 keys each** — `pluginAgentPersonaName`, `pluginAgentPerso…
**Test results**: 67+ tests pass across `locales.spec.ts` (20), `smoke.spec.ts` (44), `api-surface.…
exec
/bin/sh -lc "echo \"ARGUSIC_RESULT: {\\\"install_succeeded\\\": true, \\\"launch_succeeded\\\": tru…
 succeeded in 0ms:
tokens used
825,793

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

  • Installed in 25 minutes.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.44
Argusic Runner1/3Did not run20.000.06

Topics (from GitHub)

deepseekdeepseek-harnessdshdsh-better-sidebardsh-pluginsidebar

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/DSH-better-sidebar.svg)](https://argusic.com/subject/dsh-better-sidebar)

Questions

Does DSH-better-sidebar run?
DSH-better-sidebar runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test DSH-better-sidebar?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1499502bfa63. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test DSH-better-sidebar?
The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does DSH-better-sidebar take to install?
25 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-better-sidebar need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing DSH-better-sidebar?
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-better-sidebar?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion