DSH Git Memory

Git-backed, reviewable long-term context for DeepSeek Harness.

Status: compatibility spike / pre-alpha. The current release proves the DSH integration seams and deliberately does not store user memory yet.

Product direction

DSH Git Memory is being built around one trust invariant:

One controlled memory transaction equals one Git commit.

The intended product gives DeepSeek Harness useful context on day one, then accumulates source-backed memory during normal use. Accepted memory stays local, diffable, reviewable, and revertible.

What works today

• Installable DSH bundle with a dsh.bundle manifest.
• Stable dynamic context registered through ctx.systemPrompt.context().
• Metadata-only observation of session/event.
• A direct human command: /memory status.
• A read-only model tool: memory_status.
• Windows and Ubuntu CI.
• No transcript persistence, no background model calls, and no memory writes.

The spike records only aggregate event counts and timestamps in process memory. It never retains message or tool-result content.

Quick start from source

Prerequisites:

• Node.js 24 or newer.
• pnpm 11.
• DeepSeek Harness 0.1.0-rc.6.

git clone https://github.com/starfishwrx/dsh-git-memory.git
cd dsh-git-memory
pnpm install
pnpm verify
dsh plugin --profile web add .
dsh --profile web --dump-config

Start the Web profile, then run:

/memory status

The model can also call:

memory_status

This package has not been published to npm yet. GitHub dependency installs run the package's prepare build and therefore require explicit pnpm allowBuilds permission. Pin a commit when testing a source install.

Planned user experience

1. /memory setup gathers basic profile, project, goal, preference, boundary, and consent information.