DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Hermes Memory — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins

@lcthe/dsh-hermes-memory

Hermes Memory

DSH-native persistent memory and safe session-aware retrieval plugin.

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add @lcthe/dsh-hermes-memory@0.2.2
READMECompatibilityVersions

Compatibility and provenance

Hermes Memory is published as @lcthe/dsh-hermes-memory and currently resolves to version 0.2.2. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
web
Release source
npm
Registry updated
9/4/2026

Versions

0.2.2stable
9/4/2026

Related plugins

Loading related plugins…

Latest
0.2.2
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
279.5 kB
Files
8
Surface
web
License
MIT
Source
npm
GitHub
★ 0
Weekly downloads
0
Last push
9/4/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in memory-context.

Memory Plugin@openviking/dsh-memory-pluginOpenViking memory and context bundle for DeepSeek HarnessWeknora@wxg-prc-cpg/dsh-weknoraWeKnora knowledge retrieval tools for DeepSeek Harness (dsh): semantic search, document reading and RAG/agent answers over your own knowledge bases.Memsearch Dsh@zilliz/memsearch-dshMemSearch plugin for DeepSeek Harness: shared markdown memory across agents, with capture, pre-step context injection, memory-recall skill, and a skill-candidate review panel.Reme@agentscope-ai/remeReMe client and memory integrations for TypeScript agents

README

dsh-hermes-memory

DSH-native persistent memory, session-aware retrieval, and safe learning for DeepSeek Harness.

Status

V5 background review, V6 standing context, and the V7 consolidation foundation are implemented locally. Standing profiles and instructions are explicitly saved, bounded, persisted in the DSH storage domain, and injected once at the start of each new session. V7 now has crash-safe plan state, replacement-before-retirement execution, structured model scheduling, and native settings. V8 now has storage-backed skills and a DSH-native provider; explicit skill tools and automatic learning remain in progress.

Product boundary

This is a new DSH plugin. It does not copy Pi runtime code, Pi commands, Pi TUI, Pi branding, Pi logos, Pi screenshots, or other Pi visual assets. It reuses only general engineering ideas such as scoped memories, provenance, full-text retrieval, correction tracking, and secret scanning.

V1 scope

  • Explicit memory_save, memory_search, memory_replace, and memory_remove tools.
  • Global, user, project, and failure memory scopes.
  • DSH storage-domain persistence with schema validation.
  • Pre-write secret and prompt-injection scanning.
  • Settings namespace and a small settings card for enablement, retrieval limits, capture policy, and retention.
  • Source provenance containing session ID and event sequence when a memory comes from a DSH session.
  • session_memory_search powered by DSH's native sessionQuery service.
  • Optional V3 session-start injection of bounded reference context, off by default.

V3 scope

  • Opt-in agent/session-start injection of one bounded form: 'recall' context message per agent lifecycle.
  • Authorized global, user, and current project memories only; failure memories are not injected automatically.
  • Deterministic scope/date/ID ordering, entry limits, total character limits, resume de-duplication, and fail-soft startup behavior.

V3.1 scope

  • memory_list lists bounded records by scope/category and the current workspace.
  • memory_stats reports counts and character usage per scope.
  • lastReferencedAt advances on search hits and successful startup injection, off-path and fail-soft.
  • List/stats and reference tracking never bypass the existing exact-match workspace authorization.

V4 scope (first slice)

  • Rule-based captures from real user/message events: corrections, project conventions, and preferences.
  • Captured records carry source: 'session' provenance with session ID and event sequence.
  • Idempotency via existing provenance fields and content deduplication; no new storage tables or domain version bump.
  • Per-session capture cap, category switches, and safety scanning before every write; default off.

V4.1 scope

  • Per-session tracking of lastToolCall/lastFailure and the previous user-message sequence.
  • Corrections paired with a failed tool call in the same exchange also save a failure/tool-quirk record naming the tool.
  • A failure context is consumed at most once; captureToolContext lets users disable pairing.

V4.2 scope

  • Expired memory cleanup using lastReferencedAt ?? updatedAt as the aging anchor.
  • Failure-scope records expire after failureRetentionDays; all others after retentionDays.
  • Hard delete with count-only logging; invalid timestamps are kept; retentionEnabled can disable cleanup.
  • Sweeps run at startup and are throttled to once per hour per process on session starts.

Deferred scope

  • Automatic prompt injection on every step.
  • Vector or embedding retrieval.
  • Custom session database access.
  • Replacement of DSH chat UI or session shell.
  • A separate memory management UI is not planned: ordinary memories use the existing memory tools, while standing context is managed with memory_pin, memory_pins, and memory_unpin.

Development

The V5 background review implementation and its safety constraints are documented here:

  • docs/superpowers/specs/2026-08-27-dsh-hermes-memory-v5-background-review-design.md
  • docs/superpowers/plans/2026-08-27-dsh-hermes-memory-v5-background-review.md

The implementation plan for earlier versions lives at:

  • docs/superpowers/specs/2026-08-27-dsh-hermes-memory-v3-session-start-injection-design.md
  • docs/superpowers/plans/2026-08-27-dsh-hermes-memory-v3-session-start-injection.md

The approved design is documented at:

  • docs/superpowers/specs/2026-08-26-dsh-hermes-memory-design.md

License

MIT. The implementation will contain original DSH-specific code and will not vendor Pi project assets.