Add 'claude-code-ide' platform support for Anthropic's Claude Code IDE extension (third surface, separate from existing 'cursor' platform)

[github-actions[bot]]

Originally posted as issue #2162 by @zjl578254155
#2162

Capture hooks from Anthropic's Claude Code IDE extension — a third surface, distinct from the existing cursor platform

The gap

claude-mem already supports two surfaces:

• claude-code — the terminal CLI (npx @anthropic-ai/claude-code). ✅
• cursor — Cursor's own native AI panel, via cursor:install + beforeSubmitPrompt + .cursor/rules/ (refs #838, #633). ✅

A third surface is uncovered: Anthropic's official Claude Code IDE extension (the VSCode-style extension Anthropic ships, which also runs inside Cursor since Cursor is a VSCode fork — not the same thing as Cursor's own chat panel). On this surface MCP loads (mem-search works) but no lifecycle hooks fire → no observations, no summaries.

Reproduction

1. Worker healthy on 127.0.0.1:37701.
2. Terminal claude + a few tool calls → log shows full [HOOK] PostToolUse … → Stop → summary stored. ✅
3. Anthropic Claude Code IDE extension in Cursor + same tool calls → log shows only Claude-mem search server started / MCP server shutting down. Zero [HOOK] / [QUEUE] / [DB] entries.

17:32 [WORKER] processing status        ← end of last terminal session
19:56 [SYSTEM] Claude-mem search server started   ← IDE-ext session
   ... many Read/Bash/WebFetch calls between 19:56–20:00 ...
   ... ZERO [HOOK] / [QUEUE] / [DB] entries ...

The search server started lines confirm .mcp.json is honored — only the hook layer is silent.

Why (best guess) + precedent

The IDE extension fires hooks under a different event vocabulary (camelCase, smaller set) than the terminal CLI. Precedent: superpowers@claude-plugins-official/5.0.7 ships two hook files —

File	Event keys
hooks/hooks.json	SessionStart (PascalCase — terminal)
hooks/hooks-cursor.json	sessionStart (camelCase — IDE extension)

claude-mem's hooks/hooks.json registers PascalCase only, so nothing matches.

Structurally same as #1270 ("read now, write when hooks land") — but here hooks do fire, just under different names.

Suggested fix

Add a third platform — claude-code-ide — alongside claude-code and cursor:

1. hooks/hooks-claude-code-ide.json mirroring superpowers/hooks-cursor.json (camelCase events).
2. Re-use existing worker-service.cjs hook claude-code <event> entrypoints.
3. Optional claude-code-ide:install / :status scripts parallel to cursor:*.

Even partial coverage (sessionStart + userPromptSubmit + postToolUse) unlocks observation capture. Avoid mixing camelCase into the existing claude-code hooks.json — keep it a distinct platform, matching how cursor is its own surface.

Questions

1. Authoritative reference for the IDE extension's hook event names / set?
2. Third named platform vs. sub-mode of claude-code — preference?
3. PR welcome?

---

Env: macOS 24.3.0, claude-mem 12.4.7, Anthropic Claude Code IDE extension running in Cursor. Happy to share full logs or enumerate which camelCase events the IDE extension actually fires.