Skip to content

architecture.md

Latest commit

 

History

History
26 lines (22 loc) · 1.51 KB

architecture.md

File metadata and controls

26 lines (22 loc) · 1.51 KB
Raw

Architecture

Architecture

The pieces, top to bottom.

  • AI tools (Claude Code, Cursor, editors) reach your memory over MCP through the local daemon's /mcp endpoint (Streamable HTTP) on 127.0.0.1:4243. It exposes the frozen six tools: memory__search, memory__read, memory__write, memory__edit, memory__list, memory__delete.
  • agentage CLI - the memory, vault, setup, status, and daemon commands. Memory verbs default to the daemon; --no-daemon runs them in-process.
  • Local daemon (127.0.0.1:4243) - the single writer over the vault engine, so concurrent writes are serialized. It serves the /mcp endpoint (disable with daemon start --no-mcp or AGENTAGE_DAEMON_NO_MCP=1, and it 404s) and schedules background sync. The API is loopback-only and token-guarded.
  • Local vaults - plain markdown folders on disk, one git repo per vault, backed by the @agentage/memory-core engine. Every write commits; deletes are recoverable from history.
  • Sync channels (both optional):
    • Git remotes you host - the daemon commits, pushes, and pulls on an interval.
    • Account sync to the agentage cloud after agentage setup (OAuth 2.1 sign-in at auth.agentage.io), so the same memory follows you across machines.

Conflicts never lose a write: when both sides change the same file, the remote copy is kept alongside yours as <file>.conflict.md.