deepseek-harness
tt-a1i
Generate validated, self-contained interactive architecture, workflow, sequence, data-flow, and lifecycle diagrams from repositories or system descriptions.
Installed cleanly when we ran it
dream-num/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.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
The desktop app keeps its own profile, desktop, and only the dsh command it ships may change it — the npm-installed dsh refuses that profile. Install the command from the app menu (Manage dsh Command…), open Desktop once, quit it fully, run the line below, then reopen Desktop.
via npm
Resolves a published tarball rather than cloning the repository.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/desktop/pnpm-workspace.yaml.
Our install check ran in a web profile on npm's dsh, not in the desktop app.
What happened when we ran it
Installed cleanly when we ran it
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run yesterdayon DeepSeek Harness 0.2.2-rc.1.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
Security
No build script was blocked in our run.
Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, yesterday.
package.json declares no preinstall, install or postinstall script.
Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.
shell commands (bash, exec, spawn …)
Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.
Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.
What it is — A DeepSeek Harness plugin that puts spreadsheets, documents, slides, relational tables, and canvases in one runtime so the agent can build, edit, import, and export ordinary Office files.
Who it is for — You are driving a DeepSeek model in DSH to ship a payroll workbook, a lesson deck, or a headed weekly report, and the gap is the agent writing real .xlsx, .docx, or .pptx. If your DSH work never leaves the git repo and the terminal, this runtime does not belong on the profile.
Watch out — In a fresh profile the sandbox install succeeded and DSH registered the plugin. It executes shell commands, and Node.js 22.19 or newer is required. No other obvious pitfalls showed up.
The verdict — I would not spend a profile slot on the format catalog. I would spend it on isolated drafts I can keep or drop in the thread.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

dsh-univer-office is a DeepSeek Harness plugin that adds spreadsheets, documents, presentations, relational tables and editable canvases to a shared Univer runtime. DeepSeek Harness can use it through natural-language requests in a conversation to create or modify content, or to import existing .xlsx, .csv, .tsv, .docx and .pptx files. A .univer file can contain Sheets, Docs, Slides, Bases and Boards, with formulas and embedded content referencing other content in the same file.
Writes begin in an isolated draft rather than replacing the current version. The agent can inspect structure, recalculate or lint layouts, take screenshots, print to PDF, and leave changes for live preview, approval, merging or discard. Worktrees can be compared against a pinned trunk version or another active worktree. Reviewed work can be exported to standard Office formats such as .xlsx, .docx and .pptx.
The plugin is intended for agents that need office-style authoring, data analysis, document layout or multi-agent worktree review. It is a poor fit when only basic file manipulation is needed, or when Node.js >=22.19 is unavailable. The catalogue marks a terminal surface: dsh-univer-office reaches the terminal while carrying out its file-based office operations, so its actions should be considered alongside the agent’s terminal permissions.
The README describes no plugin-specific configuration keys or default values. DeepSeek Harness loads the plugin in the web profile, and the documented workflow is driven by natural-language requests in a conversation rather than a separate configuration file.
DeepSeek Harness uses conversational requests to create, edit, verify and export content. The README documents no additional plugin-specific command names or flags. Typical requests ask for a spreadsheet with formulas and formatting, a presentation with a specified outline, a report exported as docx, or a Base grouped by a field.
The package metadata specifies Node.js >=22.19. The plugin operates on office content in a Univer runtime. It can import xlsx, csv, tsv, docx and pptx files, and can export Sheets, Bases and related tabular content as xlsx, csv or tsv, Docs as docx, and Slides as pptx.
DeepSeek Harness can create or edit Sheets, Docs, Slides, Bases and Boards. Sheet operations include formulas, styles, tables, charts, pivots, filters, validation and images. Docs support rich text, lists, tasks, tables, images, charts, headers, footers and pagination. Slides support pages, shapes, images, tables, charts, SVG layouts and transitions. Bases provide tables, fields, records, views, formulas, filters, sorting and grouping; Boards provide editable shapes, text, connectors, images, charts and diagrams.
Every write starts in an isolated draft. DeepSeek Harness can verify changes through structured inspection, readback, recalculation, layout checks, screenshots, PDF printing and live preview. A draft or submitted worktree can be switched between View and Compare to inspect semantic changes against a pinned trunk or another active worktree.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
tt-a1i
Generate validated, self-contained interactive architecture, workflow, sequence, data-flow, and lifecycle diagrams from repositories or system descriptions.
Installed cleanly when we ran it
A workspace-based Studio for source-grounded reports, slides, tables, mind maps, quizzes, flashcards, audio and video, using DSH models and shared artifact services. Office generation requires Python 3.12+ with its dependencies and DSH_OFFICE_PYTHON configured; media rendering requires Chromium, and local ASR additionally requires whisper.cpp and a model.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
PerryLink
Deterministic industry research reports for DeepSeek Harness — company and industry research flows produce structured, verifiable reports from staged evidence.
Installed cleanly when we ran it
Roland0511
WYSIWYG Markdown editor in the DSH right sidebar, built on MarkText's muya engine: open a .md file, edit it as a rendered document, and save back through ctx.fs with a version guard.
Installed cleanly when we ran it
joeseesun
Browse UI design references and interaction examples, take design quizzes, and export learning notes as Markdown.
Installed cleanly when we ran it
PolinniZhong
Puts the Markdown documents, source files, images and video that already exist anywhere in the session workspace into the DSH sidebar, ranked by relevance to the current conversation. The default lexical mode matches your recent messages against title, summary and body locally with IDF weighting (BM25) — no model calls, no network, nothing leaves the machine. The list comes from scanning the workspace rather than from a recent-files list, so restarting DSH or opening a new session does not empty it. Results are organised into a three-tier reading order (primary / supporting / related) with a verifiable reason on every row — which field matched, which document cites this one — and one click opens an in-place preview: Markdown as rendered text, relative-path images actually drawn, source code with the host's own syntax highlighting, video streamed over HTTP Range. The same Context Pack is exposed to the agent as a knit_docs tool. Later versions added read evidence and lifecycle tracking (attribution is frozen at the moment of reading), pin / exclude (exclusion applies before retrieval, and is undoable), relation evidence (references / imports / tests, with line numbers) and an incremental index reused across restarts. Since v0.23 there is also an optional hybrid mode: it is off by default and only runs once you configure an Ollama or OpenAI-compatible embedding provider yourself. When it runs, what leaves the machine is your query text plus each candidate file's title and summary — a Markdown summary is an excerpt of the body's first paragraph (at most 60 characters), a code file's summary is its workspace-relative directory, and an image or video contributes its file name; full bodies and absolute paths are not sent, and a loopback provider keeps everything on this machine. Since v0.24 it also associates uncommitted changes: a read-only git status (fixed argv, no shell, whitelisted child-process environment) combined with the same reference / import / test / mention evidence shows which files a change is likely to drag along, and it is off by default. The benefit of semantic retrieval still awaits a real-provider run, so no recall improvement is claimed.
Installed cleanly when we ran it