MemoryRouter
DeepSeek Harness memory

DeepSeek Harness memory: profile state, made durable

DeepSeek Harness runs long sessions under a profile, and profile state is local. Long runs are exactly where losing the middle of the story gets expensive.

DeepSeek Harness. Sources checked 2026-09-25.

How DeepSeek Harness handles memory today

Harness state is organized by profile on the machine running it, so a long agent run accumulates context inside that profile and nowhere else.

Plugins are the supported extension point, and dsh-memoryrouter adds a MemoryRouter-backed memory layer with a documented config block.

What DeepSeek Harness forgets

A long run that keeps everything in one profile loses everything with that profile.

The fix with MemoryRouter

Install the plugin into your profile, add the config block, and the harness gains memory that outlives the run and the machine.

  1. 1

    Install the plugin into your profile

    Install from npm

    dsh plugin --profile <your-profile> add dsh-memoryrouter
  2. 2

    Add the memory configuration

    Add the memoryrouter entry to your profile plugin configuration with your key, then restart the profile.

    Profile config

    - id: memoryrouter
      # key and options documented in the plugin README
Install the harness plugin

Install commands, config, and limitations on the DeepSeek Harness page. 14-day free trial.

Related

DeepSeek Harness memory FAQ

Sources

Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.

Start free