xmemo-deepseek-plugin

DeepSeek Harness sessions are ephemeral: close the terminal and the context is gone. xmemo-deepseek-plugin solves this by acting as a native Cordis plugin that talks directly to the MemoryOS REST API behind XMemo, giving dsh a persistent, local-first memory layer without routing through an MCP bridge. Every write—remember, recall events, timeline entries, TODOs, decisions—lands in a local JSON store first. An offline-durable outbox queues writes when the network is unavailable, replaying idempotent operations automatically and holding non-idempotent ones for explicit confirmation, so nothing is silently lost or double-applied.

The plugin exposes 16 structured tools spanning the full memory lifecycle: recall and storage of facts and preferences, timeline event recording, active task state with restart snapshots for session resumption, TODO and decision tracking. Recall merges local token-overlap scoring with cloud results and applies a strict fail-closed bucket/scope filter, dropping any cloud item that does not exactly match the request to prevent context contamination. Authentication supports the full OAuth 2.1 + PKCE flow (Dynamic Client Registration, loopback redirect, token rotation and revocation) as well as a static API key. Deletion defaults to a recoverable soft delete. A settings card appears in dsh's Web GUI where users can connect or disconnect their XMemo account and switch between hybrid, local-only, and cloud-only modes with immediate effect—no restart required.

If you are using DeepSeek Harness for long-running development work and need cross-session persistence for project decisions, open TODOs, and working state—or simply want your memory to survive an offline dev session—this plugin offers a more native, lower-latency memory substrate than the MCP-bridge approach. It is MIT-licensed and ready to configure per dsh profile.