plugin-architecture

The memory-keeper daemon architecture uses a single long-lived process coordinating a SQLite queue and drain loop to maintain persistent state. This daemon-based design enables reliable queue-based async processing across Claude Code and Pi integrations.

The two-adapter pattern in the memory-keeper architecture connects a Claude Code SSE client and a Pi HTTP adapter to the central daemon. Both adapters share a unified workflow, enabling end-to-end processing across different interface protocols.

Start debugging the memory-keeper architecture by examining the single daemon state, then trace interactions through the SSE and REST interfaces. Verify the core library interactions and queue-based async processing to isolate integration failures.

The memory-keeper core library provides pure TypeScript modules for memory, queue, processor, and server components. This extensible architecture enables reuse and testability when planning changes or adding custom processing logic.

The memory-keeper architecture documents both SSE and REST interfaces within its two-adapter pattern. The Claude Code adapter uses SSE while the Pi adapter uses HTTP, both coordinating through the central daemon and unified core library.

The single daemon architecture in memory-keeper coordinates one process for the SQLite queue and logging. When the daemon is not running, queue-based async processing stops, making the daemon a single point of failure for persistent state operations.