Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Capture & dedup without lifecycle hooks — and what actually has hooks (research)
Research for RFC #878. Findings that drive the design; see per-app files for sources. Rule from RFC #878 that still holds: everything entering the store goes through
sanitize()→/hookor/hook/batch; never a direct wiki/DB write.
1. Revised capture map
RFC #878's core claim ("no clean automatic-capture story for closed desktop apps; Cursor is the exception") needs revision after this research:
| Surface | Capture mechanism | Effort |
|---|---|---|
| Claude Desktop Code tab (local) | Already captured: desktop runs Claude Code with user ~/.claude/settings.json → ai-memory hooks fire (agent=claude-code; a folderless session's cwd is a scratch workspace). Verified from transcripts 2026-10-08. Zero new code. |
0 |
| Claude Desktop Cowork | Unverified: on Linux its tasks run in a QEMU/KVM VM; never run on the research machine. | verify |
| Codex desktop (Codex mode) | Same host config as CLI (~/.codex/hooks.json); codex app-server, which the app runs, fires trusted hooks (verified 2026-10-08). One in-app prompt still to confirm. Then zero code. |
verify |
| Antigravity IDE / 2.0 / CLI | Native hooks (~/.gemini/config/hooks.json + .agents/hooks.json); payload has conversationId, transcriptPath, workspacePaths[], toolCall. Map to /hook observations. ai-memory already ships install-hooks --agent antigravity-cli; IDE reads the same global file. |
adapter polish |
| Zed (ACP + terminal agents) | Agent's own hooks; Zed transparent. | 0 |
| Claude Desktop Chat tab, hosted ChatGPT chat, Grok Bot | No hooks, no local store → model-discretion MCP tool calls (option a) and/or explicit capture tool. | RFC Phase 1 |
| Hosted ChatGPT plugins | Remote-only; needs published plugin + reachable server. | new surface |
What the MCP server can see server-side (all apps)
ai-memory is the MCP server, so on any MCP-connected app we observe: tool calls (name + args + results) and call timestamps, and nothing else through the MCP session. We do not see chat turns, prompts, or model output. Practical consequences:
- Server-side observation is enough for usage telemetry (which tools an app's model actually calls) and for recall-effectiveness signals, not for conversation capture.
- It is also enough to implement an explicit capture primitive the model
can be instructed to call (RFC #878 Phase-1
memory_capture_conversationidea): on apps without any hook surface this is the only in-band path, and its quality is bounded by the model's willingness to summarize.
Local-store watchers (option c) — status
Now concrete per app (paths verified locally unless noted):
~/.claude/projects/<munged-cwd>/<session>.jsonl: Claude Code-family transcripts (desktop Code tab included). Watcher optional: hooks already cover it; a watcher adds value only for hookless flows (e.g. user disabled hooks).~/.codex/sessions/**/rollout-*.jsonl+~/.codex/history.jsonl: Codex.~/.gemini/antigravity{,-ide,-cli}/brain/<conversationId>/**/transcript.jsonl: Antigravity (per hooks doc; not yet verified locally because there are no IDE chats on the machine).- Zed native agent: internal DB in Zed's data dir. Do not build on it (unstable, version-fragile); rely on ACP agents instead.
- Claude Chat tab / hosted ChatGPT / Grok Bot: no local store, so the watcher class does not apply.
A watcher/importer remains the importer-envelope (/hook/batch) pattern
from companions/ai-memory-importer; keep it out of core (RFC #878 rule).
2. Session identity & dedup design
Claude CLI ↔ Desktop (the case that prompted this)
Verified mechanics (see claude-desktop.md):
- Desktop Code sessions are Claude Code sessions: one
session_id(CLI UUID)./desktopandclaude --desktop --resume <id>move the same id across surfaces. ai-memory's(agent=claude-code, session_id)key therefore sees one session, no dedup needed. - A desktop Code session started without a project folder is a new CLI
session under an ephemeral scratch cwd
(
~/.config/Claude/scratch-workspaces/<acct>/<org>/scratch-YYYY-MM-DD-hex). An earlier version of this note attributed these to Cowork; the desktop records say otherwise (verification-2026-10.md). Two effects to design for:- Project fragmentation: every scratch dir becomes its own
auto-named project. Today that means a stream of one-off projects.
Options (product decision, not research):
- (a) detect the scratch-workspace path prefix in scope resolution and
route to a single
desktop/claude-scratchproject (keeps memory in one pool); or - (b) leave per-scratch projects but tag them
claude-desktopvia session metadata for filtering. The desktop-side record (~/.config/Claude/claude-code-sessions/.../ local_*.json) providestitle,createdAt, account/org and thelocal_* ↔ cliSessionIdmapping if we want to enrich/label, but it is an implementation detail of a closed app; treat as optional hint, not a dependency (it can move without notice).
- (a) detect the scratch-workspace path prefix in scope resolution and
route to a single
- Bridging id exposure: the desktop id (
local_*) never reaches hooks, so no collision risk with the CLI UUID.
- Project fragmentation: every scratch dir becomes its own
auto-named project. Today that means a stream of one-off projects.
Options (product decision, not research):
- Live-only correlation:
~/.claude/sessions/<pid>.jsongivesentrypoint: claude-desktop+hostSessionIdwhile a process runs. Not archival; useful at most for a tray app's "current desktop sessions" view. - The cc-socks Unix sockets (
/run/user/<uid>/cc-socks/<pid>.sock) are an internal IPC of the closed app; do not build on them.
Codex
One Codex host per user: CLI + desktop + IDE extension share ~/.codex
(config and session rollout store). Session ids are the rollout UUIDs;
(agent=codex, session_id) is already correct, and a session started in
the desktop app is distinguishable only by content/absence of TUI markers,
with no id-level split. Hosted ChatGPT/Codex-cloud sessions are cloud ids that
never touch the local store; if cloud-side capture ever matters it arrives
via export/API, mapped as a separate agent kind (e.g. codex-cloud) to
avoid double-counting with local rollouts.
Antigravity
conversationId (UUID) is the session key, identical across IDE/CLI/2.0
for the same conversation; the surface is distinguishable by the
transcriptPath prefix (antigravity-ide/ vs antigravity-cli/ vs
antigravity/). Map to ai-memory: agent=antigravity, session_id =
conversationId, cwd = workspacePaths[0] (fallback: last path; the
payload has no scalar cwd). The hook set lacks SessionStart/SessionEnd, so
derive session boundaries from first/last observation timestamps per
conversation id (ai-memory sessions are already built from observation
streams, so a Stop-hook flush marker is enough; optional).
General rule
Dedup key stays (agent, session_id); surface variants of one agent
ecosystem that share an id space stay one agent kind (claude-code covers
CLI+desktop; codex covers CLI+desktop+IDE ext; antigravity covers
IDE+CLI+2.0). Where a closed app keeps its own id (desktop local_*),
never invent capture from it; treat it as metadata only.
3. Open questions
- Codex desktop:
codex app-serverfires trusted hooks (verified 2026-10-08); one in-app prompt remains to rule out a desktop-side override. - Does Antigravity IDE honor
~/.gemini/config/hooks.jsonin practice, and doesworkspacePathsever contain >1 path on this setup? (The CLI honors.agents/hooks.json, verified 2026-10-08; the IDE is still a live test.) - Claude Desktop Chat tab: is any local conversation cache planned (desktop extensions/plugins evolve fast)? Re-check quarterly; not buildable today.
- Grok Bot
mcpBoxServersentry format: reverse-engineer only if the product gains traction with users; no docs. - Scope for scratch-workspace sessions: single
desktop/claude-scratchpool vs per-scratch projects (product decision; affects auto-scope). - Resolved (#1306): Antigravity
invocationNumrestarts at 0 on every user turn, so SessionStart is now gated per conversation (conversationId).