DeepSeek Harness 插件

dsh-ihow-memory

Install iHow Memory as a local-first shared memory plugin for DeepSeek Harness.(英文原文)

跳到安装方式

来源信息

GitHub 仓库
iHow1/dsh-ihow-memory
最近更新
2026年8月17日
分类
记忆
GitHub stars
0
载体类型
plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/iHow1/dsh-ihow-memory
插件名:dsh-ihow-memory
作者:iHow1

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

dsh-ihow-memory

Install iHow Memory as a local-first shared memory plugin for DeepSeek Harness.

The package is a thin DSH bundle. It mounts DSH's MCP client and starts an exact ihow-memory Core dependency from the plugin installation. It does not require a global iHow Memory binary and does not duplicate Core storage or governance logic.

Status

Alpha. The package targets DSH 0.1.0-rc.6 and iHow Memory Core 0.1.0-alpha.31.2.

Core and plugin lifecycle

ihow-memory is the Core package: it owns storage, retrieval, governance, and the MCP contract. dsh-ihow-memory is only the DSH adapter and distribution bundle. Installing this plugin does not replace a global ihow-memory command or modify another runtime's adapter.

The plugin pins an exact Core version so an existing DSH installation cannot change behavior when Core publishes a new release. The two packages therefore use independent versions:

  • A Core release does not automatically require a plugin release.
  • Release a new plugin when the pinned Core must move for a compatible feature or security fix, when the MCP contract changes, or when DSH integration changes.
  • Test the pinned Core through DSH before each plugin release; do not widen the Core dependency range.

Runtimes share durable memory only when they intentionally use the same MEMORY_ROOT or IHOW_MEMORY_ROOT. DSH keeps its index and runtime state under its own IHOW_MEMORY_STATE_ROOT, so shared memory does not imply shared mutable runtime state.

Install

dsh plugin --profile web add dsh-ihow-memory@next
dsh web

For Headless:

dsh plugin --profile headless add dsh-ihow-memory@next
dsh --profile headless "Check memory status"

Restart the selected DSH profile after installation. The agent receives iHow Memory tools under DSH's stable mcp__ihow-memory__... namespace.

Storage

By default the plugin uses iHow Memory's managed local storage:

~/.ihow-memory/<workspace>-<hash>/

It keeps DSH index state under:

~/.ihow-memory/.state/dsh/

The active DSH workspace determines the managed memory space. For persistent profile configuration, override paths on the plugin row:

- id: ihow-memory
  config:
    memoryRoot: /path/to/existing/memory
    stateRoot: /path/to/writable/dsh-state
    workspace: /path/to/workspace-identity

home, memoryRoot, stateRoot, and workspace accept absolute paths, relative paths, and ~/.... Plugin fields take precedence over environment variables. Existing environment-based installs remain compatible:

VariablePurpose
IHOW_MEMORY_HOMEManaged iHow Memory home directory
MEMORY_ROOT or IHOW_MEMORY_ROOTExisting shared memory directory
IHOW_MEMORY_STATE_ROOTRuntime index/state directory
IHOW_MEMORY_CWDWorkspace identity override
IHOW_CAPTURE_FLOOR=0Disable the bounded startup capture sweep

When migrating an existing MCP row, copy its MEMORY_ROOT to memoryRoot and IHOW_MEMORY_STATE_ROOT to stateRoot before removing the old row. Never run both rows against the same store. The plugin never deletes memory when it is updated or uninstalled.

Verify

For a deterministic persistence receipt, run the bundled Core flow:

npm run demo:cross-session

It writes a random marker, searches it from a new process, forgets it, verifies it is hidden after another restart, restores it, and verifies it is searchable again. The full DSH Host flow uses the official DSH tool registry and is documented in [DEMO.md](DEMO.md).

For the manual flow, ask DSH to call memory status, search a known fact, write a low-risk candidate, start a new session, and search for the same fact. For the full verify-first handoff path, call memory.continue and validate the returned live anchors before acting on its narrative.

Set DEMO_RECEIPT_PATH to retain the Host result as JSON; the temporary memory space is still removed after the assertions complete.

Update and remove

dsh plugin --profile web update dsh-ihow-memory
dsh plugin --profile web remove dsh-ihow-memory

Removing the plugin removes the DSH bundle only. It does not remove ~/.ihow-memory or a configured shared memory root.

Security

The plugin spawns the bundled Core over stdio. It stores no model credentials and uses DSH's scrubbed child-process environment. Memory can contain sensitive project context; review candidates before promotion and never store secrets, tokens, private keys, passwords, or cookies.

Development

npm install
npm run verify
dsh plugin --profile web add "link:/absolute/path/to/dsh-ihow-memory"

License

Apache-2.0