COMPARE · COMPARISON: AGENT MEMORY

OpenViking alternatives in 2026: 7 agent memory and context tools compared

AUTHOR · XERJ documentation team · REVIEWED BY · XERJ engineering team · PUBLISHED · 2026-11-15 · UPDATED · 2026-11-15
SHORT ANSWER · UPDATED 2026-11-15

What are the best OpenViking alternatives in 2026? Mem0 and Hindsight extract facts with a language model. Honcho models people over time. Letta is a full stateful agent. Cognee builds a graph from documents. ReMe and XERJ store memory with no model call on write; XERJ semantic recall reached 94.7% top 5 in our open test.

Key number: OpenViking organizes agent context as a viking:// virtual filesystem with L0 abstracts, L1 overviews and L2 full content, and needs an embedding model and a VLM to run. (as of 2026-11-15 · source: github.com/volcengine/OpenViking)

Last checked: 2026-11-15. Every third-party fact on this page was re-read from the tool's own docs or repository on that date.

TL;DR The best OpenViking alternative depends on what your agent needs from memory. Mem0 and Hindsight extract facts with a language model. Honcho models people and sessions over time. Letta is a complete stateful agent. Cognee builds a graph from documents. ReMe and XERJ store memory with no model call on write; in our open test XERJ semantic recall found the right memory in the top 5 for 94.7% of questions.

PASTE THIS TO YOUR AI AGENT — IT DOES THE REST Act as a coding agent. Read https://xerj.org/llms.txt and https://xerj.org/compare/openviking-alternatives-2026, then pick a memory and context layer for this project from the table on that page. If you pick XERJ: install it, start a node with --embed-mode neural, store five facts about this repo with POST /_memory/project, and recall each one. Report what you chose and why.

OpenViking, from Volcengine, is a context database for AI agents with 42,270 GitHub stars. It keeps knowledge, memory and skills as a virtual filesystem under viking://, and each folder carries a short abstract and an overview so the agent reads full files only when it needs them. Background: what agentic memory is.

Try it: pick by job

Which OpenViking alternative fits

OpenViking

A viking:// filesystem for knowledge, memory and skills, with short abstracts and overviews before full content. Needs an embedding model and a VLM.

Recall figures from the XERJ agent memory benchmark of 2026-10-31. Features from each project README, checked 2026-11-15.

Summary table

Top 5 is the share of 75 questions where the right memory came back first to fifth in our AI agent memory benchmark. Not tested means the tool was not in that round.

ToolLicenceShapeModel on writeTop 5 in our testStars (2026-11-15)
OpenVikingAGPL-3.0viking:// filesystem with L0, L1, L2 layersyes: embedding model and VLMnot tested42,270
Mem0Apache-2.0LLM-extracted facts plus embeddingsyes by default, infer=false turns it off86.7% / 88.0% raw69,018
HindsightMITretain, recall and reflectyes, LLM keynot tested61,202
HonchoAGPL-3.0peers, sessions and background reasoningyesnot tested8,135
LettaApache-2.0stateful agent with memory blocksyes, it is an agentnot tested3,846 (Letta Code)
CogneeApache-2.0graph of entities plus chunksoptional, GLiNER works without a keynot tested33,334
ReMeApache-2.0BM25 plus optional embeddingsno70.7% (BM25 default)3,807
XERJApache-2.0stored text, BM25 or semantic recall, plus file searchno94.7% (semantic) / 73.3% (BM25)19,118

When to choose OpenViking instead

Choose OpenViking when you want one browsable filesystem for everything an agent knows. Agents navigate it with ls, tree, read and grep, sessions become Markdown memories you can edit, and the layered summaries keep context small. It ships a memory plugin for Claude Code, Codex, Cursor and others. Its README reports LoCoMo accuracy of 80% to 83% for three agent integrations, measured by the vendor with Doubao models.

Mem0 and Hindsight: facts extracted by a model

Choose Mem0 when you want a language model to turn conversations into a tidy list of facts, as a library, a self-hosted server or a cloud platform. Choose Hindsight when you want memory that learns from what the agent does, with retain, recall and reflect operations and an MCP endpoint. Both call a model on write. More options: Mem0 alternatives 2026.

Honcho and Letta: memory for stateful agents

Choose Honcho when your agent talks to many people and you want it to reason about each of them in the background, managed or self-hosted. Choose Letta when you want a complete stateful agent with memory blocks, not a memory API you call from your own agent.

Cognee and ReMe: graphs or plain files

Choose Cognee when your memory starts as documents and conversations you want turned into a graph of entities and relationships; it runs with a local GLiNER model and no LLM key. Choose ReMe when you want fast, light memory with BM25 by default: it answered queries in 1.4 ms in our test. Details: XERJ vs ReMe.

XERJ: a new way for AI to search for data

XERJ stores exactly the text your agent sends with POST /_memory/{namespace} and recalls it with search. With --embed-mode neural and the built-in MiniLM model, semantic recall found the right memory in the top 5 for 94.7% of questions; the default embedder is lexical feature hashing, and BM25 recall scored 73.3%. The same node indexes your code, docs and data files, so memory and document search share one API and one MCP server. XERJ is single-node and makes no model call on write, so it does not summarise sessions for you.

How this page was checked

Licences, install lines and features were read from each project's README on 2026-11-15, and star counts came from the GitHub REST API the same day. Recall figures come from our AI agent memory benchmark of 2026-10-31. OpenViking, Hindsight, Honcho, Letta and Cognee were not in that round, and vendor figures are labelled as the vendor's.

Try it with XERJ

Use the Copy the prompt button and paste it into your coding agent. It picks a memory layer from this table and, if it picks XERJ, stores five facts about your repository and recalls them.

Read next

Mem0 alternatives 2026, best MCP memory servers for Claude Code, Mem0 vs Zep vs Letta vs Cognee and Claude Code memory.

FAQ

What is OpenViking?

OpenViking is an open-source context database for AI agents from Volcengine. It stores knowledge, memory and skills as a virtual filesystem under viking://, with short abstracts and overviews so an agent can judge relevance before it reads full content. It needs an embedding model and a VLM.

What is the closest alternative to OpenViking?

For memory plus documents behind one API, Cognee and XERJ are the closest: Cognee builds a graph from documents and conversations, and XERJ stores agent memory and indexes your files in one local node. For memory alone, Mem0, Hindsight and Honcho are the best known.

Which OpenViking alternative needs no model on write?

ReMe and XERJ store memories with no language model call. Cognee runs without an LLM key using a local GLiNER model. OpenViking, Mem0 and Hindsight use a model on their default write path.

Was OpenViking in your benchmark?

Not yet. Our first agent memory round ran on a shared CPU machine, and OpenViking needs an embedding model and a VLM. Its own README reports LoCoMo results measured with Doubao models, which we quote as the vendor's figures.

Which one works with Claude Code?

OpenViking, Hindsight, Honcho and XERJ all connect to Claude Code over MCP, and OpenViking also ships a hooks plugin. See our list of MCP memory servers for Claude Code for install lines.

How was this page checked?

Licences, install lines and features were read from each project's README on 2026-11-15, and star counts came from the GitHub REST API the same day. Recall figures come from our agent memory benchmark of 2026-10-31.

Evidence

Related