dsh-ai-memory

Configuration

Optional. The defaults are correct for a standard ai-memory install, and the plugin behaves identically with no config: block at all.

- insert:
    - id: ai-memory
      name: dsh-ai-memory
      config:
        exePath: /usr/local/bin/ai-memory   # default: platform standard location
        dataDir: /home/me/.local/share/ai-memory  # default: let the CLI decide
        agentKind: claude-code              # default: claude-code
        sweep: true                         # default: true
        preflight: true                     # default: true
        timeoutMs: 120000                   # default: 120000

Key	Default	Meaning
exePath	Windows: %LOCALAPPDATA%\Programs\ai-memory\ai-memory.exe; elsewhere: ai-memory from PATH	Path to the ai-memory executable.
dataDir	unset	ai-memory data directory. Leave unset unless you use a non-standard location; the CLI then resolves its own, which is what the hooks use.
agentKind	claude-code	The agent kind recorded in ai-memory's store. See the note below — this is not a free choice.
sweep	true	The abandoned-session safety net. Set false to disable it entirely.
preflight	true	Log one line at startup naming the ai-memory version, data directory, and server it found.
timeoutMs	120000	Per-finalize-session timeout.

Why agentKind should stay claude-code

ai-memory recognises a fixed set of agent kinds — claude-code, codex, cursor, open-code, opencode2, pi, omp, zero, kiro-cli, pool, zcode — and rejects anything else outright. There is no dsh kind.

DSH reaches ai-memory through the Claude Code hook bridge, so every captured DSH session is stored as claude-code. That is simply what the store contains, and finalize-session must be told to look there. Passing anything else — including the CLI's own default, which is codex — will match no session ever.