Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(install-mcp): stop recommending DSH's Claude Code hook bridge for capture

AkitaOnRails2b6809d34ffb
diff --git a/crates/ai-memory-cli/src/cli.rs b/crates/ai-memory-cli/src/cli.rs
index 2a249d3c..a10b6d3d 100644
--- a/crates/ai-memory-cli/src/cli.rs
+++ b/crates/ai-memory-cli/src/cli.rs
@@ -2680,8 +2680,8 @@ pub enum McpClient {
/// config: the client is a Cordis plugin entry
/// (@deepseek-ai/dsh-mcp-client) inside a profile's cordis.patch.yml.
/// This integration is print-only (--apply is refused); merge the
- /// rendered insert list into the profile patch. Pair it with DSH's
- /// @deepseek-ai/dsh-hooks-claude-code bridge for lifecycle capture.
+ /// rendered insert list into the profile patch. No lifecycle capture is
+ /// claimed.
#[value(alias = "deepseek-harness", alias = "deepseek_harness")]
Dsh,
}
diff --git a/docs/mcp-install.md b/docs/mcp-install.md
index 85060953..5b98de44 100644
--- a/docs/mcp-install.md
+++ b/docs/mcp-install.md
@@ -516,9 +516,10 @@ the default stateless HTTP endpoint and carries `Authorization: Bearer <token>`
when `--auth-token` (or a configured server token) is present.
DSH ships a bridge that runs an existing Claude Code `hooks.json` or settings
-file (`@deepseek-ai/dsh-hooks-claude-code`), so lifecycle capture for a DSH
-session is possible by pointing that bridge at a Claude Code hook config. ai-memory
-does not install or manage it, and the bridge delivers only seven Claude Code events
+file (`@deepseek-ai/dsh-hooks-claude-code`). Pointing it at ai-memory's Claude
+Code hooks is not a supported capture path: those hooks report every event as
+`agent=claude-code`, so DSH sessions would be stored as Claude Code sessions.
+ai-memory does not install or manage the bridge, and it delivers only seven Claude Code events
(`SessionStart`, `UserPromptSubmit`, `PreToolUse`, `PostToolUse`,
`Stop`, `SubagentStart`, `SubagentStop`) — `PreCompact` and
`SessionEnd` are not delivered, and its `SessionStart` injection runs
diff --git a/docs/support-matrix.md b/docs/support-matrix.md
index 62ab0f4d..7c6b6d95 100644
--- a/docs/support-matrix.md
+++ b/docs/support-matrix.md
@@ -39,7 +39,7 @@
| VS Code Copilot | MCP-only | `.vscode/mcp.json` for Copilot agent mode; no lifecycle hooks (Copilot does not expose them yet). |
| Zed | MCP-only | Native remote MCP under `context_servers` in Zed's user `settings.json`; no lifecycle hooks or managed-workstream support. |
| Muse Code | MCP-only | `install-mcp --client muse` merges a native streamable-HTTP entry with bearer `headers` into the snake_case `mcp_servers` map of `~/.config/muse/settings.json`, preserving sibling servers. The writer adds the mandatory `"schema_version": 1` when absent (without it every `muse` command fails at startup) and never rewrites an existing value, and it sets `"mode": "optional"` because Muse's default `required` aborts the whole run when the server is unreachable. Skills need no extra step: Muse reads `~/.agents/skills`, which `install-skills` already writes. Lifecycle capture and managed workstreams are not claimed — Muse documents a hook surface, but the output contract of its `SessionStart` event is not specified. |
-| DeepSeek Harness (DSH) | MCP-only | `install-mcp --client dsh` prints a Cordis patch fragment (a `- insert:` item for `@deepseek-ai/dsh-mcp-client`) to merge into `$DSH_HOME/profiles/<profile>/cordis.patch.yml`; DSH has no fixed MCP config file, so `--apply` is refused. Pair the snippet with DSH's `@deepseek-ai/dsh-hooks-claude-code` bridge to reuse an existing Claude Code hook config for capture, but ai-memory does not install it and only seven Claude Code events are delivered (`PreCompact` and `SessionEnd` are not), with a detached `SessionStart`. No managed workstream. |
+| DeepSeek Harness (DSH) | MCP-only | `install-mcp --client dsh` prints a Cordis patch fragment (a `- insert:` item for `@deepseek-ai/dsh-mcp-client`) to merge into `$DSH_HOME/profiles/<profile>/cordis.patch.yml`; DSH has no fixed MCP config file, so `--apply` is refused. Lifecycle capture is not claimed: DSH's `@deepseek-ai/dsh-hooks-claude-code` bridge can run a Claude Code hook config, but ai-memory's Claude Code hooks would report DSH sessions as `agent=claude-code`, and the bridge delivers only seven Claude Code events (`PreCompact` and `SessionEnd` are not), with a detached `SessionStart`. No managed workstream. |
| Hermes Agent | Supported | `install-hooks --agent hermes` (alias `hermes-agent`) prints a ready-to-paste `hooks:` block for `~/.hermes/config.yaml`. Hermes splits each configured `command` with `shlex.split` and runs it with no shell, passing the event JSON on stdin, so the entries invoke the native `ai-memory hook` command (exec form, like Zero and ZCode — no script bundle is staged); ai-memory never writes that YAML file, which is yours to edit and which Hermes itself gates behind its hook-acceptance prompt (`hooks_auto_accept`). Two tool events are wired, `pre_tool_call` → `pre-tool-use` and `post_tool_call` → `post-tool-use`; their `tool_name` / `tool_input` payload drives concrete session attribution, tool-family titles, and capture exclusions. Session lifecycle (recall, prompt capture, session-end, automatic handoff) is owned by the community-maintained [`ai-memory-hermes-plugin`](https://github.com/MrLuciano/ai-memory-hermes-plugin) memory provider, so no hook-driven `session-end` is installed and nothing is duplicated; review that plugin's compatibility matrix, install/uninstall scripts, and secret handling before enabling it. No first-party `install-mcp` client and no managed workstream are claimed yet, and because Hermes ignores session-start hook stdout a pending handoff is recovered through MCP (`memory_handoff_list` then `memory_handoff_accept`). |
| GrizzyBot | Supported | [GrizzyBot](https://github.com/Foscoe63/GrizzyBot), a native macOS agent app, ships its own ai-memory bridge: it posts lifecycle events to `/hook` with `agent=grizzybot` (alias `grizzy-bot`) and talks to `/mcp` directly, so there is nothing for `install-hooks` or `install-mcp` to write. Sessions are attributed to `grizzybot`, and its Claude Code-shaped tool payloads (`tool_name`/`tool_input`/`tool_use_id`) are stored as closed-schema tool families, never tool names or arguments. The bridge is maintained in the GrizzyBot repository; review it before pointing it at a shared server. No managed workstream. |
| LLM/auth providers | Supported | Anthropic, OpenAI, OpenAI OAuth/Codex, GitHub Copilot, Gemini, OpenCode (Go and Zen), OpenAI-compatible endpoints, and generic OIDC device auth for native hooks. |