dsh-cc-dream-memory

dsh-cc-dream-memory

Claude Code-style auto memory and Dream for DeepSeek Harness.

Your agent remembers across sessions. Every change Dream proposes is one you can review and undo.

English · [简体中文](https://github.com/muuuuuuuuuer/dsh-cc-dream-memory/blob/main/README.zh.md)

Before and after

Tell your agent something once, then ask in a new session. Same project, same model, same question. The only difference is the plugin.

Without the plugin, the agent replied "Both noted" and promised not to recommend the old script, then recommended it in the next session. With the plugin, it saved two notes on its own and used them.

We ran the second session three times on each side. The deploy step was legacy-deploy.sh in all three runs without the plugin, and make release in all three with it. The picture shows the first run of each. The project is made up, and its README still names the old script on purpose. This is one example, not a benchmark. See [Status](#status).

Install

Requires Node 22 or newer and DeepSeek Harness 0.2.2-rc.1 or newer.

dsh plugin --profile web add dsh-cc-dream-memory

Restart DeepSeek Harness and start a new session. If dsh is not on your PATH, use npx:

npx @deepseek-ai/dsh plugin --profile web add dsh-cc-dream-memory

In the desktop app, open Plugins → Add plugin and enter dsh-cc-dream-memory.

You can also install directly from GitHub:

dsh plugin --profile web add github:muuuuuuuuuer/dsh-cc-dream-memory

Dream

Notes go stale. Here, three sessions changed the facts while five older notes stayed as they were. A Dream read those sessions and proposed six changes, and all six were applied.

You can apply only some of the changes, and one command undoes the whole Dream.

The interface

A Memory tab sits next to Chat in every session, and the status bar shows how many notes the project has.

Dream. Open any change to read it, then apply only what you agree with.

Settings. Switches for memory and automatic Dreams, and the rules for what is worth saving.

It follows the host's light and dark themes. Every screenshot is real, from DeepSeek Harness, with a made-up project.

Why this one

Bring your memories. Notes are plain Markdown in a Claude Code-compatible layout: a MEMORY.md index plus one file per topic. Already have Claude Code memories? /memory import brings them over, and you can open every file in your editor.

Dream shows its sources. Dream reads whole sessions, not samples. Each new fact has to quote the conversation, and a quote the plugin cannot find in the transcript gets the change dropped. /memory dream preview prints the quotes:

[2] write feedback_handoff_notes.md (changed)
    quote: "For handoff notes I want the conclusion first, then risks, with no headings."

Nothing is final. Dream only proposes a plan. You pick the changes, a backup is taken first, deleted notes go to a trash folder, and one command undoes the whole Dream. Automatic Dreams are off until you turn them on.

Try it

Run these in a session.

1. Tell your agent something worth keeping, or save it yourself:

   /remember --type=project Release notes live in docs/releases.md

2. Start a new session. The MEMORY.md index loads once and stays frozen for that session. When a message clearly matches a memory, the plugin attaches that memory to the step.

3. After a few sessions, make a plan. This changes nothing:

   /memory dream run --dry-run
   /memory dream preview

4. Apply what you agree with, and undo it if you change your mind:

   /memory dream apply-ops 0,2
   /memory dream undo

You can do steps 3 and 4 on the Dream tab of the Memory view too. See the [command reference](https://github.com/muuuuuuuuuer/dsh-cc-dream-memory/blob/main/docs/commands.md) for everything else.

Coming from Claude Code

/memory import ~/.claude/projects/