dsh-flymemory: A DSH plugin That Gives DeepSeek Harness Long-Term Memory

What Does It Do?

FlyMemory is a DSH plugin for DeepSeek Harness that gives the harness long-term memory, so you stop re-explaining the same context every session. It runs a local memory engine as an MCP service and plugs it into the harness, exposing 15 memory tools plus two hooks that quietly record what you have been working on and pull the relevant bits back when they matter. Everything stays on your machine: the service listens on a local address, the library is a single file under your DSH home, and nothing is sent anywhere. It is maintained by aujurd22 under the MIT license and written in Python.

Core Features

• 15 memory tools: cover storing, searching, state tracking, consolidation and forgetting, all exposed to the model under one shared prefix.
• Automatic recall and capture hooks: every prompt is stored and matching memories are appended to the turn, and a recovery pack of recent activity is delivered on session start; neither hook can block a turn.
• Fused retrieval with decay: dense embeddings and keyword matching are combined, older entries fade, and results come back with id, age and provenance.
• State and conflict handling: track "the current value of X" per entity key while retiring the old one, and surface contradictory pairs or valuable entries that are fading.
• Local single-file storage: the library lives in one file under your DSH home, and multiple harness windows share one engine and one library.

How to Use This Plugin?

Once enabled in DSH, the model can call the memory tools directly, and you can simply ask it to remember a decision or look up an earlier conclusion. On startup the plugin checks the local memory service port: if a service already answers there it is reused, if the port is free the bundled engine starts in the background, and if something else owns the port the plugin says so and leaves it alone rather than killing a process it did not start. Cold starts are slow because the engine imports its inference dependencies before it can listen, typically 15-20 seconds; the default wait is 25 seconds and the client reconnects on its own. If the engine cannot start at all, the harness still boots, you just do not get the tools and the reason is in the log. Behavior can be tuned through environment variables documented in the README settings section.

How to Troubleshoot This Plugin?

When the engine fails to start, DSH still boots normally and only the memory tools are missing; the reason is written to the log, so you can tell whether an interpreter is absent, dependencies are incomplete, or the port conflicts. If another process owns the port, the plugin only reports it and leaves things as they are instead of terminating a process it did not start, so you need to deal with the occupant yourself. Slow cold starts are expected, and the connecting client reconnects on its own after a timeout; follow the official instructions to confirm the prerequisites are satisfied.