dsh-univer-office

Give DeepSeek Harness a real office environment. Univer Office Plugin brings spreadsheets, docs, slides, canvases, relational tables, and more into one runtime, with connected data, validation, versioned changes, and isolated worktrees for multi-agent collaboration.

Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 5ce30f6eb88c

TypeScript, Apache-2.0 licensed. The project labels itself: deepseek harness, deepseek harness plugin, dsh, dsh plugin, office, office harness and univer.

dsh-univer-office runs, with stand-ins for the services it depends on. An Argusic agent installed it in 23 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 repository installs with the project-pinned Node 22 and pnpm 11.23.0, builds lib/ and artifacts/, passes lint, typecheck, format:check and the entire test suite (10 suites green, 99 comparison tests), and the built Univer Viewer boots and renders its UI in headless Chrome in this container.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.33 (measured)
recorded runs
1
last tested
stars
747
forks
62
open issues
21
watchers
3
size
66 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-univer-office, 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.

  • test/host-settings-profile.mjs requires an independently installed DSH runtime (UNIVER_DSH_RUNTIME_ROOT) which was not present8 minutes
  • No Chrome/Chromium system browser found, so screenshot/PDF/layout tests failed to launch Chromium5 minutes
  • System Node.js is v18.19.1 but the project requires >=22.19.0 (error TS error / pnpm 11.23.0 itself refuses v18)3 minutes
  • pnpm is not installed inside the container2 minutes
  • repo-wide format:check fails on checked-in files src/client/conversation/univer-turn-definition.ts and test/fixtures/header.html2 minutes
Install time
23 minutes
Cold machine to finish
22 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
pnpm test exited 0 with all suites green (host OK, migration passed, preview formula OK, integration smoke OK, client smoke OK x2, client layout OK, unit-comparison-viewer 16 files/99 tests passed, skills OK, telemetry passed); additionally a headless Chrome navigated the served built Viewer at http://127.0.0.1:33241/univer-viewer/ and the rendered page read 'No file specified Add ?file=<absolute path to the .univer>' with no page errors
Model tokens used
1,552,458
Exact commit tested
5ce30f6eb88c
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

Sun Oct 18 10:38:16 UTC 2026
exec
/bin/sh -lc 'export PATH=/tmp/node-v22.23.3-linux-x64/bin:/home/runner/.local/bin:$PATH && pnpm -v …
 succeeded in 109ms:
11.23.0
v22.23.3
All verification is complete. Final state: the repository installs, builds, and the full test suite…
2026-10-18T10:38:30.529760Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-18T10:38:30.529805Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
tokens used
1,552,458
All verification is complete. Final state: the repository installs, builds, and the full test suite…

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 23 minutes.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks92.000.33

Topics (from GitHub)

deepseek-harnessdeepseek-harness-plugindshdsh-pluginofficeoffice-harnessuniver

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-univer-office.svg)](https://argusic.com/subject/dsh-univer-office)

Questions

Does dsh-univer-office run?
dsh-univer-office runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 23 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test dsh-univer-office?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ce30f6eb88c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test dsh-univer-office?
The run that produced this verdict cost $0.33: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does dsh-univer-office take to install?
23 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-univer-office need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing dsh-univer-office?
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-univer-office?
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.

Discussion