Skip to main content

How to use dsh-memory-evolve

Injects five-track layered memory into DSH (global/user/project/project-key+git-branch/daily), self-evolving backend review, todo/skills/prompt/canvas management, COI external AI agent scheduling, and cross-device memory sync.

This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.

This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

dsh-memory-evolve

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add github:csyangwen/dsh-memory-evolve

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

  • id: dsh-memory-evolve
  • id: dsh-memory-evolve
  • 用户档案：你的偏好、公司、沟通习惯——AI 每回合都能看到；
  • 全局事实：环境、工具、惯例等长期知识；
  • 项目关键记忆：当前项目的约定、决策、架构、踩坑，自动注入上下文，重要结论可标记只在某个 git 分支生效；

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

Do I need to manually install anything else after installation to run it?

No. The package includes cordis.patch.yml (dsh.bundle.patch declaration) by default; after dsh plugin add, the host side registers automatically; the only action needed is to restart dsh web as prompted. Manually inserting the same id again in the profile patch will cause the loader to report a duplicate loader entry id.

Where is memory and todo data stored? How do I move it to another computer?

Stored in <DSH_HOME>/memories by default (DSH_HOME defaults to ~/.dsh), all local files. After enabling the "Memory Sync" module (syncEnabled), you can configure cross-device sync in the Web UI: project tracks use dedicated branches in the project code repository, global tracks use a separate shared memory repository; remote push always requires you to actively click "Sync and Push".

Will AI write things to memory without permission?

It won't write without permission. The user/memory/key tracks follow an "AI suggestion → You confirm" flow; suggestions go to SUGGESTIONS.jsonl and only take effect after you adopt them in the memory tab's "Pending Confirmation"; project/daily tracks are auto-written (per turn progress) but content also stays local.

After installing, I don't see the "Canvas/Broadcast/Session Orchestration" tabs?

These are independent sub-modules and are closed by default. You need to go to "Memory Evolve Settings → Configuration" to enable the corresponding switches (canvasEnabled/broadcastEnabled/sessionEnabled etc.); the tab will only appear after enabling, and when disabled the tool is completely uninstalled (not taking up space in the model tool list).

What Node version is needed? What third-party packages does it depend on?

The plugin itself only uses Node built-in modules (fs, path, child_process, crypto, etc.), with zero runtime third-party dependencies. Node version requirement is not explicitly declared in package.json, but the import syntax is ESM and lib uses node:fs prefix, so Node 22+ is recommended.

Does uninstalling the plugin also clear the memories that were written?

No. dsh plugin --profile web remove only uninstalls the plugin itself; the memory directory (agreed as ~/.dsh/memories and ~/.agents/skills) is preserved as-is; if you need complete deletion, manually delete the corresponding directories.

Can I wake up another session across processes?

No. The de_session module only supports creating/waking sessions within the same DSH process; programmatic wakeup across instances/machines is not possible; after process restart it can already automatically resume offline sessions before waking.

Do external AI agents (kimi/codex/grok/hermes) need to be installed separately?

Yes. The COI module (coiEnabled) only provides a scheduling framework; the specific adapted CLI agents (kimi/codex/grok/hermes etc.) need to be installed separately on your machine and configured with executable paths in "Settings"; the plugin does not include these CLIs.

— source: plugin_wiki.faq_json

Compatibility

  • DSH: 未声明（package.json 无 engines/peerDependencies；描述中提及 260810+ 快照以使用部分能力如会话图片附件）
  • Node: 未声明（仅使用 Node 内置模块，建议 Node 22+）

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule