aoyamabf-max/dsh-obsidian-memory ↗★ 0

dsh-obsidian-memory

Store DSH agent memory as Markdown notes in an Obsidian vault: sidebar panel, 7 agent tools, BM25 recall with token budgets, decay and archiving, and GitHub Contents API sync.

Package
dsh-obsidian-memory
Compatibility
Unverified
Harness peer range
>=0.2.0-rc.1 <0.3.0-0
Cordis peer range
>=4.0.1 <5.0.0
Version
0.3.1
License
MIT
Last updated
Nov 2, 2026

Install

$npx -p @deepseek-ai/dsh dsh plugin --profile web add github:aoyamabf-max/dsh-obsidian-memory

Configuration

All settings live in the plugin's Config schema, so they show up in DSH's own settings UI. Every field has a default; an empty config is valid.

FieldDefaultMeaning
vaultPath""Absolute path to the vault. Empty = auto-discover from Obsidian.
folder"Memories"Subfolder for memory notes, relative to the vault root.
maxNoteBytes262144Notes longer than this are truncated (hard cap; raising it has no effect).
repo""owner/name to sync to. Empty = no sync.
branch"main"Branch to push to.
tokenFile""File holding a GitHub token. Empty = ~/.dsh/dsh-obsidian-memory/token.
denyFile""Secret blacklist, one literal per line. Empty = ~/.dsh/dsh-obsidian-memory/deny.txt.
syncEnabledtrueWhether the timer runs.
syncMinutes30Sync interval in minutes (minimum 5).
forgettingEnabledfalseAllow decay/archive to actually write. Preview works either way.
decayFactor0.9Multiplier applied per decay pass.
pruneThreshold0.15Below this importance, a note becomes eligible for archiving.

Setting up GitHub sync (optional)

  1. Create a private repository. Memory can contain hostnames, paths and internal decisions.
  2. Create a fine-grained token with Contents: read and write on that repo only.
  3. Save it: mkdir -p ~/.dsh/dsh-obsidian-memory && printf '%s' '' > ~/.dsh/dsh-obsidian-memory/token
  4. Set repo to owner/name in the plugin config.

The token is never written into the plugin config or the repository. Sync state (a path → sha256 map) lives in ~/.dsh/dsh-obsidian-memory/sync-state.json, so only changed notes are pushed.

Keeping secrets out

The plugin refuses to push a note containing a secret, and counts it under blocked rather than failed — the two mean different things. Two layers:

  • Built-in patterns (ship with the code): github_pat_, gh[pousr]_, AKIA, sk-, BEGIN … PRIVATE KEY, 密码[:=是]….
  • Your own blacklist at ~/.dsh/dsh-obsidian-memory/deny.txt — one literal string per line, # for comments. Put your own server addresses, passwords and key names here. This file stays on your machine and is never read into the source tree.