dshbase
中文

Blog · Pulse

Community Pulse #3

September 1, 2026 · dshbase · a recurring report on the DeepSeek Harness community

This is the third edition of Community Pulse. Since #2 on August 25, the repo crossed 207,000 stars with zero open issues still holding. We pulled the live discussion board again and found the week's signal: the vault thread is now the busiest in the repo, the model-list snapshot ask went unanswered for another week, and the install-hang cluster from #2 finally shows real movement. Here's what changed.

The snapshot

207,387 stars at the time of writing, up from the ~158k we tracked in our American-tools piece. Discussion volume keeps compounding — the board's newest threads are now past #4,400, roughly +60% since Pulse #2 eight days ago. The category mix on recently-active threads is unchanged in shape: General dominates, Ideas and Q&A cluster around the same pain points, and Show Your Plugins keeps producing the most interesting reads.

The headline: the vault thread won't stop climbing

In Pulse #2 we flagged dsh-vault — an encrypted credential vault — as the busiest thread on the board at 184 comments. A week later it's at 207 comments and still the most active discussion in the repo. That's not a one-off popularity spike; it's a durable demand signal. As agents move onto shared machines, CI runners and multi-user setups, storing secrets safely stops being a nice-to-have and becomes the thing people will switch tools over. The follow-on effect is visible in the plugin marketplaces too: secret-handling and lifecycle management are becoming the differentiators, not the tool count.

Follow-ups from Pulse #2: what moved

  • The install hang finally shows movement. #3786 — the loudest install-hang thread (npx pegging the CPU in a dependency-resolution loop) — picked up more comments through August 28. The workarounds still hold (pin the release tag, pre-warm a clean registry cache), but the thread's continued activity suggests the fix isn't in a released build yet. #4236 (the npm 10.9.8 peer-resolution variant) stayed quiet, which may mean it's a dup of the same root cause.
  • Subagent model-inheritance is still open. #455 and #4311 both saw updates through the end of August — #4311 on August 28. This remains the sharpest correctness bug for third-party-provider users: subagents inherit the model from creation time (or an expired default) instead of the session's current model, and every subagent call explodes with "no API key." It's a trust-killer, and it's still unresolved.
  • The session-corruption family gained members, then quieted. #4385 (empty callId on tool/result events raising SessionPersistenceCorruptionError) got a reply on August 25 and has been quiet since — possibly fixed in a nightly, possibly just unpicked-up. Worth re-checking next edition.

Feature radar: the model-list snapshot is still the loudest ask

#3816 — dsh serving model lists from a bundled pi-ai catalog snapshot instead of pulling them live from the gateway — gained comments through August 27 with no sign of a fix. Models that already work on OpenCode Go still don't surface until a release ships. The community's hand-declared OpenAI-compatible model workaround keeps getting recommended in threads, which is itself a signal: users are willing to hand-configure to get a model that should just appear.

The perennial asks are alive and well: #76 (headless --host 0.0.0.0) now sits at 54 comments, and the CLI demand cluster is real: #67 (26 comments), #102 and #45 all keep asking for a proper terminal client. The pattern across all three: the web UI is fine for a single session, but heavy users want a keyboard-first, scriptable interface. It's the same "power users will open the hood" tell we called in our review.

Bug radar: Windows, workspaces and the platform tax

  • Windows-specific friction is the quiet theme. #53 — fast mode on Windows calling Linux terminal commands — got updates through August 30. #37 (the Firefox directory-picker dialog popping up in the background) also resurfaced. Both are "the platform tax": the core is great, but cross-platform edges keep generating the same class of bugs.
  • Workspace & directory picker issues cluster. #30 — "directory picker failed" — is at 24 comments and still drawing reports through August 30. It's a different failure from the install hang but the same shape: the first interaction with the tool is where it breaks.
  • Environment noise. #71 (failed to load .env: EISDIR when a directory is named .env) and #100 (node:zlib module error on dsh web) are the week's entry-level tripping points. Small, but they're the first thing a new installer sees.

Ecosystem: the count war cools, discovery heats up

The 7,000-plugin claim from #2423 hasn't moved much this week — the count war appears to have plateaued while the discovery problem takes over. #1597 ("1,700+ plugins, how do I find the one for me?") keeps accumulating answers, and the community marketplace project #2687 — lifecycle management, security gating, one-click restart — stayed active through August 31. The marketplaces are converging on the same bet we're making at dshbase: does it run beats how many exist. Our verified directory exists for exactly that reason.

What "memory" means here

One of the most-upvoted Ideas threads, #14 ("求一个memory能力" / "we want a memory capability"), is at 49 comments and still climbing through August 30. It's worth reading carefully, because the thread is really asking for three different things at once: persistent cross-session context, a way to store and retrieve project knowledge, and better long-session behavior. The harness's append-only session logs (our deep dive) solve reproducibility, not memory — and the community is starting to feel that gap. Expect memory/context plugins to be the next vault-style demand wave.

What to watch next

  • The vault thread is the canary. When #1457 keeps growing past 207 comments, it's telling you where the real deployment pain is. Watch for official secret-management support or a surge of vault-style plugins.
  • Subagent model-inheritance (#455/#4311) remains the sharpest correctness bug. It either gets fixed fast or becomes the community's standard "works on defaults, breaks on yours" complaint.
  • Live model lists (#3816) and the CLI demand cluster (#67/#102/#45): two "make the tool fit how I actually work" asks that keep compounding.
  • Memory is the next frontier. The 49-comment memory thread plus the vault demand point the same direction: as agents get trusted with more, the community wants them to remember more — safely. See how we audit plugins in the meantime.

Community Pulse is a recurring report. Want us to track a discussion, or spotted a correction? Open an issue on the dshbase repo.

All articles →