Update from two days later: we shipped the Claude Code HTTP hooks integration.
The injection problem I mentioned earlier, of memory not loading automatically without system prompt config is now partially solved for Claude Code. SessionStart hook auto-injects memory capabilities, TaskCompleted tracks turns, SessionEnd persists everything.
It's also clarified our thinking on the protocol question: lifecycle hooks (SessionStart, SessionEnd, ContextCompaction) feel like the right abstraction for ambient memory. If other tools did the same, you'd configure memory once and it would work everywhere.
The injection problem I mentioned earlier, of memory not loading automatically without system prompt config is now partially solved for Claude Code. SessionStart hook auto-injects memory capabilities, TaskCompleted tracks turns, SessionEnd persists everything.
It's also clarified our thinking on the protocol question: lifecycle hooks (SessionStart, SessionEnd, ContextCompaction) feel like the right abstraction for ambient memory. If other tools did the same, you'd configure memory once and it would work everywhere.
Any thoughts or feedback on the topic are welcome