Blog · Concept
What “everything is a plugin” actually means
August 20, 2026 · dshbase · rewritten field guide
“Everything is a plugin” sounds easy when you apply it to tools and skills. It gets weird when sessions, sandboxes, and the filesystem show up on the same list. That is the point DeepSeek Harness is making — and the reason a plugin directory that only counts GitHub stars is not enough.
This piece is a substantial rewrite of ideas popularized in Chinese WeChat coverage (notably APPSO’s “大起底” essay on DSH plugins). We keep the architecture argument, drop the marketing copy, and add what we see when we actually install community plugins.
Harness first: the model is the hire, not the office
A strong new hire does not start work the moment they walk in. Someone still has to give them a desk, accounts, permissions, shared drives, and the history of what the team already tried. Swap “hire” for “model” and that whole onboarding kit is the harness: tools, files, memory, sandbox, recovery, and the loop that turns “look → act → observe → decide” into a workday.
Same model, different harness → different product feel. That is why Agent comparisons that only quote model cards miss the real delta.
Ordinary plugins: add a printer to a finished office
Classic plugins assume a finished product. Chrome already browses; an ad blocker is additive. Claude Code / Codex-style extensions mostly live in the same zone:
- Tool / MCP — register another callable action
- Skill / instruction files — inject on-demand guidance
- Hooks — validate or log around tool calls
- Subagents — farm out a slice of work
Useful, but the trunk stays sealed: how the main loop turns, how context is assembled, how sessions persist, how the sandbox is wired. You can add a printer; you usually cannot replace the badge system.
DSH plugins: replace office modules, not just gadgets
DSH’s claim is closer to swappable office systems. Attendance used to be a fixed machine; now any implementation that can identify a person, stamp a time, and record a location can play the role. Filesystems work the same way for an agent: the consumer cares about read/write/path/error contracts, not whether the bytes live on local disk or a remote sandbox.
That is why “everything is a plugin” is not a synonym for “lots of marketplace tiles.” It is a bet that harness seams — model adapter, session log, agent loop, FS, sandbox — can be providers behind stable interfaces.
Cordis in one paragraph (for installers)
Under the hood, a running dsh is a Cordis service tree on a shared ctx. Plugins inject the services they need; registration is designed to be revocable on unload. Official docs push a hard logging rule: model-visible means logged — anything the model sees must be reconstructible from the append-only session event stream. Composition happens in config layers (bundle → profile → home patch → --patch), which is why dsh --profile web --dump-config matters: you can see what you actually booted.
Pi went thin-core (four file/bash tools, everything else as extensions). DSH goes further: even pieces that feel like “the core” are meant to be replaceable. More freedom; more version-skew and supply-chain risk. That trade-off is the product.
What this means on dshbase
Once the core is pluggable, “it exists on GitHub” stops being a useful quality signal. A bad provider can change boot behavior for everyone on that profile. We only mark directory entries verified after a real install path — including webonly plugins that need a live Web/CDP check — and we publish the failure classes on the audit page.
If you want the fatigue side of the same debate (npm vs git-source, ESM breaks, missing dsh.bundle), read our earlier piece on plugin philosophy. The short version: modularity without curation just moves the debugging onto you.
Takeaway
DSH is not interesting because “DeepSeek shipped a plugin store.” It is interesting because it asks whether the onboarding kit around a replaceable model can itself be modular. Power users will love that. Everyone else still needs presets, verified installs, and a directory that answers “does it run?” before “how many stars?”