DeepSeek Harness Memory Bundle

Give DeepSeek Harness (dsh) cross-project and cross-session long-term memory. Once installed, every conversation automatically recalls relevant memories and captures new content, and the model gets the OpenViking tools and the openviking-memory skill without any extra setup.

Source: examples/dsh-memory-plugin

Install

DSH shares the installer with the other memory plugins. It asks for your language (English/中文), which harnesses to install, the download source, and your OpenViking credentials; every step is idempotent—re-running it is entirely safe.

bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)

In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror (or pick "TOS mirror" at the download-source prompt):

bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)

When DSH is selected, the installer asks which profile to install into and defaults to web. Pass --dsh-profile <name> to answer it up front.

After using it for a while, start a new conversation and ask about something you mentioned earlier—it will remember.

1. Configure the connection — write ~/.openviking/ovcli.conf (url, api_key, optional account/user), or set OPENVIKING_URL and OPENVIKING_API_KEY. Using pure local mode (http://127.0.0.1:1933, no authentication)? Skip this—the bundle defaults to the local setup.

2. Add the bundle to a profile:

   bashCopy

   dsh plugin --profile web add @openviking/dsh-memory-plugin
   

   dsh plugin forwards to pnpm inside the profile directory, so any profile name works; web is the one dsh creates for you on first use.

3. Check that the profile picked it up:

   bashCopy

   dsh --profile web --dump-config
   

   The output should contain an openviking-memory plugin group.

Don't have ovcli.conf yet? See the Deployment Guide → CLI.

To remove it: dsh plugin --profile web rm @openviking/dsh-memory-plugin.

Verify

Start dsh --profile web and open a conversation. You should see an OpenViking context injection at the top of the session, and the model should have mcp__openviking__* tools available. Ask it about something from an earlier session to confirm recall.

If nothing appears, set OV_DEBUG_LOG=/tmp/ov-dsh.log and check that file.

How it works

The bundle runs inside DSH as a Cordis plugin rather than as external hooks, so it follows the session in-process. At session start it injects your OpenViking profile block and an index of available memories. Before every model step it searches OpenViking with the current input and appends what it finds to that step as a durable message, so the injection replays with the session and is visible to compaction. It captures user, assistant, and (optionally) tool-result messages straight from DSH's event stream, and commits to OpenViking once pending tokens cross the threshold, keeping the ten most recent messages live. Writes that fail land in a pending queue and replay at the next session start.

Each DSH session maps to dsh-<session-id> in OpenViking, and every subagent gets its own session.

The model-facing surface is the OpenViking MCP tool set, reached through the same stdio proxy the other memory integrations use and published under an mcp__openviking__ prefix. Because that proxy runs once per profile, mcp__openviking__remember stores into a short-lived server-side session rather than the current one—automatic capture still records the conversation itself—and tool calls carry the actor peer resolved at startup. Set OPENVIKING_PEER_ID when one process serves several workspaces and tool calls need exact attribution. The bundle also ships the shared openviking-memory skill, so the model knows when to search, read, and write.

Accidental filesystem or shell calls on viking:// URIs are blocked with a hint pointing at the right OpenViking tool.

Credentials resolve from OPENVIKING_* environment variables, then ~/.openviking/ovcli.conf, then ~/.openviking/ov.conf — the same chain the Claude Code, Codex, OpenCode, and pi integrations use. The bundle reloads them when those files change.

Behavior knobs live in the profile's Cordis patch entry:

- insert:
    - id: openviking-memory
      name: '@deepseek-ai/cordis-plugin-group'
      group: true
      isolate:
        openvikingMemory: true
      config:
        - id: openviking-memory-runtime
          name: '@openviking/dsh-memory-plugin'
          config:
            recallTokenBudget: 2000
            scoreThreshold: 0.35
            captureToolResults: false
            commitTokenThreshold: 20000

Credentials given in the patch win over the environment; behavior toggles read the environment first. The full list is documented in the bundle README.

Troubleshooting

See also

• Capability Reference