hmem vs tradememory-protocol
hmem: hmem is a memory system for AI agents that persists project context across sessions, devices, and AI providers. It uses a 5-level lazy loading architecture to minimize token usage while retaining full details. It supports auto-logging, background checkpoints, and cross-platform sync.; tradememory-protocol: TradeMemory Protocol provides a persistent memory layer for trading agents, enabling them to recall past trades with context, discover patterns, and evolve strategies autonomously. It features outcome-weighted recall, cognitive memory architecture, and an evolution engine for strategy discovery. Available as an MCP server for integration with Claude and other agents.
TL;DR
AI coding assistants that need to maintain project context across sessions
- Your trading agent can already execute and you want it to remember each trade with its reasoning, regime and outcome.
- You want recalled patterns weighted by outcome, with confidence, sample size and out-of-sample checks.
- You trade forex on MT5 and want trade sync.
- You take the Sharpe 3.84 result as a forecast: it is the project's own BTC backtest.
- You cannot afford LLM calls for the evolution engine, or the risk that it invents overfitted strategies.
- You are looking for an execution or broker tool: it is a memory layer.
Side-by-Side Comparison
hmemtradememory-protocolFeatures
hmemtradememory-protocolUse Cases
hmemtradememory-protocolFAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.