AgentIndex icon
AgentIndex
hmem logo
hmem
★ 24
vs
rekal logo
rekal
★ 53

hmem vs rekal

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.; rekal: rekal provides long-term memory for LLMs via an MCP server. It stores memories in a local SQLite file and retrieves them using hybrid search (BM25 keywords + vector semantics + recency decay). It works with any MCP-capable agent like Claude Code, Codex CLI, and OpenCode.

01

TL;DR

hmem logo
hmemMemory & Context · ★ 24

AI coding assistants that need to maintain project context across sessions

Read hmem full review →
rekal logo
rekalRAG / Knowledge Base · ★ 53

Persistent memory for coding agents across sessions to remember user preferences and decisions

Read rekal full review →
02

Side-by-Side Comparison

Field
hmem logohmem
rekal logorekal
Category
Memory & Context
RAG / Knowledge Base
Stars
★ 24
★ 53
License
MIT
MIT
Install Command
npm install -g hmem-mcp && npx hmem init
pip install rekal
Updated
3mo ago
1mo ago
Open Source
Yes
Yes
Website
↗ Visit
↗ Visit
GitHub
↗ GitHub
↗ GitHub
Tags
ai-agents, ai-tools, claude
llm, mcp, mcp-server
03

Features

hmem logohmem
015-level lazy loading to minimize token usage
02Automatic session logging and background checkpoints via Haiku
03Cross-provider and cross-tool support
04Project-based memory organization
05Encrypted sync across devices
rekal logorekal
01Local SQLite storage, no cloud or API keys
02Hybrid search combining BM25 keywords, vector semantics, and recency decay
03MCP server compatible with various coding agents
04Comprehensive tool-based memory management (store, search, update, delete, prune)
05Smart write operations with supersede and linking for knowledge evolution
04

Use Cases

hmem logohmem
↳AI coding assistants that need to maintain project context across sessions
↳Multi-device workflow where different agents continue the same project
↳Knowledge management for personal AI assistants
rekal logorekal
↳Persistent memory for coding agents across sessions to remember user preferences and decisions
↳Storing project-specific knowledge and conventions without external services
↳Maintaining a searchable history of agent interactions and decisions
FAQ

FAQ

What is the difference between hmem and rekal?
Both hmem and rekal are in the Memory & Context category. hmem has 24 stars, while rekal has 53 stars.
Which is better, hmem or rekal?
The best choice depends on your use case. Choose hmem if AI coding assistants that need to maintain project context across sessions, and rekal if Persistent memory for coding agents across sessions to remember user preferences and decisions.
Is hmem free or open source?
Yes, hmem is open source on GitHub (MIT).
Is rekal free or open source?
Yes, rekal is open source on GitHub (MIT).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related

Alternatives to hmem →Alternatives to rekal →hmem details →rekal details →