{"docs":[{"id":8827,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory İncelemesi: %90,4 Yeniden Hesabımızda Tuttu, Artıları ve Eksileriyle","slug":"honcho-memory-review","language":"tr","excerpt":"Honcho'nun ham benchmark dosyalarını yeniden saydık: %90,4'lük LongMemEval S skoru birebir tekrarlanıyor, LoCoMo'daki üstünlük ise aynı soru kümesiyle sayıldığında yalnızca Haiku'ya göre 6,3 puan. Artılar, eksiler, gerçek fiyatlandırma ve Honcho'yu kimlerin kullandığı burada.","body":"# Honcho Memory İncelemesi: %90,4 Yeniden Hesabımızda Tuttu, Artıları ve Eksileriyle\n\n**Honcho memory**, Plastic Labs'in AGPL-3.0 lisanslı [AI ajanları için bellek katmanı](/tr/blog/yapay-zeka-ajan-bellegi-rehberi), LongMemEval S'te %90,4 aldığını söylüyor. 28 Ekim 2026'daki testimizde ham sonuç dosyalarını yeniden saydık ve aynı 452/500 sonucunu bulduk. LoCoMo'da iki taraf da aynı 1.540 soruyu yanıtladığında, Honcho'nun düz Claude Haiku 4.5'e üstünlüğü yayımlanan 14,3 değil, **6,3 puan**.\n\nİyi bir bellek. Daha küçük bir fark. Gerçek ödünler.\n\n## Honcho Memory'ye Değer mi? Karar Tek Tabloda\n\nAjanınız bir kişiyi aylar boyunca modellemek zorundaysa Honcho'yu kullanın; doküman RAG'i, anlık hatırlama ya da kapalı kaynaklı fork için başka bir araç seçin.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements), özel bellek katmanları arasındaki tek **AGPL-3.0** seçeneği (Mem0, Letta ve cognee Apache-2.0, LangMem MIT lisanslı) ve bulut sürümü, ingestion ücretinin üstüne her sorgu için ayrıca reasoning ücreti kesiyor.\n\n| Soru | Cevap |\n|---|---|\n| Yönetilen sürüm fiyatı (kontrol: 2026-10-28) | 1M ingest edilen token başına $2; reasoning sorgusu başına $0.001 ile $0.50; `context()` sınırsız; $5 ücretsiz kredi |\n| Self-host için gerekenler | pgvector'lu Postgres, bir deriver worker, tool calling destekleyen bir LLM anahtarı |\n| Benchmark'lar | LongMemEval S %90,4, LoCoMo %89,9 (şirketin kendi bildirimi; aynı soru kümesiyle fark +27,8 ve +6,3) |\n| En uygun olduğu iş | Tek bir kişiyi zaman içinde modelleyen ajanlar |\n| Şunlar için başka araç seçin | Doküman RAG'i, sonraki turda hatırlama, kapalı kaynaklı fork'lar ([bellek araçları sıralamamızda](/tr/blog/en-iyi-yapay-zeka-ajan-bellek-araclari) Honcho 3. sırada) |\n\nEski incelemeler hâlâ $100 ücretsiz kredi yazıyor. Dokümanlar şimdi $5 diyor, kartla birlikte aylık $5 daha.\n\n## Honcho Memory nasıl çalışır?\n\nUygulamanız peer'ler arasındaki mesajları yazıyor, arka plandaki bir worker bunları düz dille sorgulayabileceğiniz ya da context olarak çekebileceğiniz çıkarımlara dönüştürüyor.\n\nPeer, kullanıcı ya da ajan olan herhangi bir katılımcı. [Honcho dokümanlarındaki](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) v3 quickstart bütün akışı gösteriyor (kaynak kod [GitHub](https://github.com/plastic-labs/honcho)'da):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` düz dille sorulan soruları yanıtlıyor. [Hibrit BM25 + vektör arama](/tr/blog/hibrit-arama-bm25-vs-vektor) mesajları ve conclusion'ları (Honcho'nun türettiği olgular) buluyor. `session.context(summary=True, tokens=10_000)` ise prompt için [token bütçeli bir context](/tr/blog/context-engineering-rehberi) döndürüyor.\n\nReasoning asenkron çalışıyor. Yeni bir olgu bir sonraki okumada değil, deriver çalıştıktan sonra görünüyor; README'deki `representation` endpoint'i düşük gecikmeli yol.\n\n## Honcho'nun %89,9'luk LoCoMo skoru tutuyor mu? Ham dosyaları yeniden hesapladık\n\n%89,9 ve %90,4'ün ikisi de Plastic Labs'in ham dosyalarından tekrarlanıyor; ancak LoCoMo'da aynı soru kümesiyle sayıldığında Haiku'ya göre fark 6,3 puan.\n\n28 Ekim 2026'da [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) deposundan üç sonuç dosyasını yeniden saydık (test edilen Honcho commit'inin adını taşıyan `a1d689b` klasörü). Yayımlanan sütun [honcho.dev/evals](https://honcho.dev/evals) sayfasındaki, yani şirketin kendi bildirimi.\n\n| Çalıştırma | Yayımlanan | Bizim sayımımız | Aynı soru kümesiyle fark |\n|---|---|---|---|\n| LongMemEval S, Honcho | %90,4 (baseline %62,6) | 452/500 | +27,8 |\n| LoCoMo, Honcho | %89,9 | %89,9, 1.540 soru | yok |\n| LoCoMo, yalnızca Haiku 4.5 | %75,6 | 446 adversarial soruyla %75,4; aynı 1.540 soruda %83,6 | +6,3, +14,3 değil |\n\nTestimiz farkın nereye gittiğini gösteriyor. Yayımlanan baseline, Haiku'nun %46,2 aldığı 446 adversarial soruyu içeriyor; Honcho'nun çalıştırmasında ise hiç adversarial soru yok. Plastic Labs'in kendi [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) yazısı “Haiku alone scores 83.9%” diyor, bu bizim %83,6'mıza yakın. Yani evals sayfası iki farklı soru kümesini karşılaştırıyor.\n\nKısa geçmişlerde Honcho'yu seçme nedeni daha yüksek doğruluk değil, daha az token. 16K ile 26K token arasındaki [LoCoMo](https://arxiv.org/abs/2402.17753) geçmişleri her 200K pencereye sığıyor ve [ConvoMem](https://arxiv.org/abs/2511.10523) yaklaşık 150 konuşmanın altında tam context'in %70-82'ye ulaştığını buldu.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S farklı: geçmiş başına yaklaşık 115K token olduğunda +27,8'lik üstünlük geçerli kalıyor. Bir kapsam notu: bu çalıştırmalar Aralık 2025 kurulumuyla, Haiku 4.5 dialectic ile yapıldı. Açık kaynak repodaki yapılandırma varsayılan olarak `gpt-5.4-mini` kullanıyor, ama bu yalnızca reponun varsayılanı; Plastic Labs üretimde yayımlamadığı farklı modeller çalıştırıyor.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Geliştiriciler Honcho'yu neden seçiyor?\n\nHoncho'nun kazandığı yer **kullanıcı modelleme**: kişinin kim olduğuna dair sürekli güncellenen bir resim tutuyor ve bu bellek kişiyi ajan araçları arasında takip ediyor.\n\nRakip Hindsight'ın yapımcısı Vectorize, Mart 2026 tarihli [Hermes bellek sağlayıcıları karşılaştırmasında](https://vectorize.io/articles/hermes-agent-memory-providers-compared) Honcho'yu kullanıcının davranışsal modeli olarak tarif ediyor, “not just a fact store”. Her gerekçenin bir tuzağı var.\n\n| Gerekçe | Kanıt | Tuzak |\n|---|---|---|\n| Kişiyi modelliyor | “Great on knowing who YOU are” ([r/hermesagent, Mayıs 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` canlı bir LLM çağrısı, yani her soru gerçek bir gecikme ekliyor |\n| Araçlar arasında tek bellek | Claude Code, Codex, Cursor, OpenCode, OpenClaw ve Hermes için plugin'ler, ayrıca `mcp.honcho.dev` üzerinde barındırılan ya da kendin kurabileceğin açık kaynak bir [MCP sunucusu](/tr/blog/claude-code-icin-en-iyi-mcp-sunuculari) | Şimdilik yalnızca metin; belgeler için OCR desteği çok sınırlı |\n| Kullanıcı testlerinde doğruluk | Qwen3.5 4B üzerinde altı sağlayıcılı bir karşılaştırma: Honcho “performed the best” ([r/hermesagent, Ağustos 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Plugin'in varsayılan ayarlarıyla “almost 3 times the tokens of the next best performer” |\n| Gizlilik | Self-host edenler bunu gerekçe gösteriyor ([Elkim, Nisan 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (eksilere bakın) |\n\nPazarlamanın gerçeğin önüne geçtiği yer token tasarrufu. Ana sayfa %60-90 diyor, ama [evals sayfası](https://honcho.dev/evals) LongMemEval S'te %89, LoCoMo'da %52, BEAM 100K'da %16 gösteriyor. Ana sayfada alıntılanan bir geliştirici ise %10-15 bildiriyor.\n\n## Honcho'yu kimler kullanıyor, kimler için uygun?\n\n28 Ekim 2026'ya kadar geçen ayda 542.206 Python SDK indirmesi, Honcho'nun gerçek kullanıcıları olduğunu gösteriyor; çoğu Hermes ve kodlama ajanları etrafındaki geliştiriciler.\n\n```stats\ncaption: Benimsenme sinyalleri, erişim tarihi 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai indirmesi, son bir ay\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk indirmesi, 27 Eylül - 26 Ekim\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub yıldızı, 954 fork\n    source: GitHub API\n```\n\nAna sayfa, logo şeridini “Used by developers at” diye etiketliyor. Bu, şirket çapında sözleşmeler ya da vaka çalışmaları değil, bu kurumlardaki tek tek geliştiriciler demek.\n\n| Grup | honcho.dev'den örnekler |\n|---|---|\n| Kurumsal şirketler | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI ekipleri | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Araştırma | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research'ün [Hermes Agent](/tr/blog/hermes-agent-v0-15)'i Honcho'yu bir bellek plugin'i olarak sunuyor (`hermes plugins install honcho`) ve [Hermes Honcho dokümanları](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) `honcho_profile`'dan `honcho_conclude`'a kadar beş araç listeliyor.\n\nPopülerlik oy birliği demek değil. X'te yapılan 138 cevaplı bir Hermes anketinde ([Ekim 2026](https://x.com/HermesWatcher/status/2114492238659305561)) Markdown notları birinci (27), Hindsight ikinci (25), Honcho üçüncü (22) oldu.\n\n- İyi uyum: companion'lar, eğitmenler ve koçluk ajanları\n- İyi uyum: Claude Code, Codex ve Cursor arasında paylaşılan kişisel kodlama ajanları\n- Kötü uyum: doküman RAG'i, sonraki turda hatırlama, kapalı kaynaklı fork'lar\n\n## Honcho'nun artıları ve eksileri: doğruluk için neyden vazgeçiyorsunuz?\n\nHoncho'nun doğruluğu gerçek; bedeli gecikme, token yükü, ağır bir self-host yığını ve AGPL, o yüzden dördüne de bütçe ayırın.\n\nSelf-host için [pgvector](/tr/blog/qdrant-vs-chroma-vs-pgvector-karsilastirma)'lu Postgres, bir deriver worker ve tool calling destekleyen bir LLM gerekiyor (repo yapılandırmasındaki varsayılanlar: `gpt-5.4-mini`, `text-embedding-3-small`). CLI; API, deriver, Postgres ve Redis'i başlatıyor, Docker Compose da çalışıyor.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # küçük batch'leri hemen işle\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Artılar: Honcho yerini nerede hak ediyor\n\n- Geliştiricilerin “seni tanıyor” diye tarif ettiği kullanıcı modelleme\n- Sayımımızdaki en güçlü uzun geçmiş sonucu: LongMemEval S'te +27,8\n- Açık kaynak, self-host edilebilir; Claude Code, Codex, Cursor, Hermes ve daha fazlası için plugin'ler\n\n### Eksiler: size neye mal oluyor\n\n- Gecikme. Geliştiriciler `minimal` dialectic izinde 9,1 sn ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) ve her Hermes API turuna eklenen 2,16 sn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)) bildiriyor. Ana sayfadaki “~200 ms”, `context()` hakkında satıcının kendi iddiası.\n- Sorgu maliyeti. Ayda 20K token ekleyen 10.000 kullanıcı için ingestion **$400**, ama her birinin 30 Low-tier sorgusu **$3,000** (Minimal: $300). Honcho faturanızı ingestion değil, sorgu katmanı belirliyor.\n- Self-host bakımı ve bağımlılık. API, deriver, Postgres, Redis ve bir LLM'i kendin çalıştırıyorsun. Embedding'ler dışa aktarılamadığı için bulut ile self-host arasında geçiş yapmak mesajları yeniden oynatmak demek ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. Bir karşılaştırma yazısı, self-host etmenin uygulamanızın kaynağını açmaya zorladığını söylüyor. Bu abartı: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html), Honcho'yu değiştirdiğinizde ve kullanıcılar ona ağ üzerinden eriştiğinde devreye giriyor. Mem0, Letta ve cognee Apache-2.0, LangMem MIT lisanslı; yani Honcho özel bellek katmanları arasında copyleft'e sahip tek istisna. Hukuki tavsiye değildir.\n\nKarar vermeden önce quickstart'ı $5 krediyle, gerçek bir konuşma kaydıyla çalıştırın.\n\n## Sık sorulan sorular\n\n### Honcho memory ücretsiz mi?\n\nKısmen. Bulut sürümü $5 kredi veriyor, kartla birlikte aylık $5 daha; $5M altında yatırım almış startup'lar $1,000 kredi alabiliyor. Self-host için AGPL-3.0 kapsamında lisans ücreti yok, ama kendi LLM ve embedding faturalarınızı ödüyorsunuz.\n\n### Honcho'yu kapalı kaynaklı bir SaaS'ta kullanabilir miyim?\n\nEvet, uygulamanız değiştirilmemiş bir Honcho sunucusunu API üzerinden çağırıyorsa. Honcho'yu değiştirip ağ üzerinden sunarsanız AGPL §13, değiştirilmiş Honcho kaynağını sunmanızı şart koşuyor. Kendi uygulamanız kapalı kalır. Hukuki tavsiye değildir; fork yapacaksanız bir avukata danışın.\n\n### Honcho mu Mem0 mu Hindsight mı: hangisini seçmeliyim?\n\nEn hızlı başlangıç için Mem0 (Apache-2.0), token tasarrufu için Hindsight (MIT), kullanıcı modelleme için Honcho. Bir geliştirici Hermes'te Hindsight'ın “used far fewer tokens” olduğunu bildiriyor ([X, Ekim 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0'nun blogu Honcho'nun herkese açık benchmark'ı olmadığını söylüyor, oysa 2025-12-19'dan beri 21 ham sonuç dosyası yayımladı. [Tam sıralama](/tr/blog/en-iyi-yapay-zeka-ajan-bellek-araclari) burada.\n\n```references\ntitle: Kaynaklar\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 dk okuma","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S skoru %90,4, yeniden hesabımızda doğrulandı, arkada soluk bir bellek düğümü grafiği","seo":{"metaTitle":"Honcho Memory İncelemesi: Artılar, Eksiler, Yeniden Hesaplanan Benchmark","metaDescription":"Honcho memory'ye değer mi? Testimizde %90,4'lük benchmark skorunu yeniden ürettik. 2026 için artılar, eksiler, gerçek fiyatlar ve kullanıcıları burada."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:09.179Z","createdAt":"2026-10-28T16:06:34.083Z","_status":"published"},{"id":8826,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho memory: 90,4 % håller i vår omräkning, plus för- och nackdelar","slug":"honcho-memory-recension","language":"sv","excerpt":"Vi räknade om Honchos råa benchmarkfiler: poängen 90,4 % på LongMemEval S stämmer exakt, och försprånget på LoCoMo över enbart Haiku är 6,3 poäng när siffrorna jämförs på samma frågor. Här är för- och nackdelarna, det verkliga priset och vem som faktiskt använder det.","body":"# Honcho memory: 90,4 % håller i vår omräkning, plus för- och nackdelar\n\n**Honcho memory**, Plastic Labs AGPL-3.0-licensierade [minneslager för AI-agenter](/sv/blogg/guide-ai-agent-minne), uppger 90,4 % på LongMemEval S. Vår testning den 28 oktober 2026 räknade om de råa resultatfilerna och landade på samma 452 av 500. På LoCoMo, där båda sidor besvarar samma 1 540 frågor, är Honchos försprång över vanliga Claude Haiku 4.5 **6,3 poäng**, inte de publicerade 14,3.\n\nBra minne. Mindre försprång. Verkliga kompromisser.\n\n## Är Honcho memory värt att använda? Domen i en tabell\n\nAnvänd Honcho när din agent ska bygga en modell av en person över månader; hoppa över det för dokument-RAG, omedelbar återkallning eller en stängd källkodsfork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) är det enda **AGPL-3.0**-alternativet bland de dedikerade minneslagren (Mem0, Letta och cognee är Apache-2.0, LangMem är MIT), och molntjänsten debiterar resonemang per fråga ovanpå inläsningen.\n\n| Fråga | Svar |\n|---|---|\n| Hanterat pris (kontrollerat 2026-10-28) | $2 per 1M inlästa tokens; $0.001 till $0.50 per resonemangsfråga; `context()` obegränsat; $5 i gratis kredit |\n| Självhostning kräver | Postgres med pgvector, en deriver-worker, en LLM-nyckel med stöd för tool calling |\n| Benchmarks | LongMemEval S 90,4 %, LoCoMo 89,9 % (självrapporterade; försprång på samma frågor +27,8 och +6,3) |\n| Bäst för | Agenter som bygger en modell av en person över tid |\n| Välj något annat för | Dokument-RAG, återkallning i nästa tur, stängda forkar ([vår rankning av minnesverktyg](/sv/blogg/basta-ai-agentminnesverktyg) placerar Honcho som nummer 3) |\n\nÄldre recensioner nämner fortfarande $100 i gratis kredit. Dokumentationen säger nu $5, plus $5 i månaden med kort.\n\n## Hur fungerar Honcho memory?\n\nDin app skriver meddelanden mellan peers, och en bakgrundsworker gör om dem till slutsatser som du kan fråga efter på vanlig svenska (eller engelska) eller hämta som kontext.\n\nEn peer är vilken deltagare som helst, användare eller agent. Snabbstarten för v3 i [Honcho-dokumentationen](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) visar hela flödet (källkod på [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` besvarar frågor med vanligt språk. [Hybrid BM25 + vektorsökning](/sv/blogg/hybridsokning-bm25-vs-vektor) hittar meddelanden och slutsatser, alltså Honchos härledda fakta. `session.context(summary=True, tokens=10_000)` returnerar [kontext inom en tokenbudget](/sv/blogg/context-engineering-guide-sv) för en prompt.\n\nResonemanget är asynkront. Ett nytt faktum dyker upp när deriver har körts, inte vid nästa läsning; `representation`-endpointen i README är den väg som har låg latens.\n\n## Håller Honchos 89,9 % på LoCoMo? Vi räknade om de råa filerna\n\n89,9 % och 90,4 % går båda att reproducera från Plastic Labs råa filer, men på LoCoMo är försprånget över enbart Haiku 6,3 poäng när man jämför på samma frågor.\n\nDen 28 oktober 2026 räknade vi om tre resultatfiler från [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (körningsmappen `a1d689b`, uppkallad efter den Honcho-commit som testades). Kolumnen med publicerade siffror är självrapporterad på [honcho.dev/evals](https://honcho.dev/evals).\n\n| Körning | Publicerat | Vår omräkning | Försprång på samma frågor |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90,4 % (baslinje 62,6 %) | 452/500 | +27,8 |\n| LoCoMo, Honcho | 89,9 % | 89,9 %, 1 540 frågor | n/a |\n| LoCoMo, enbart Haiku 4.5 | 75,6 % | 75,4 % med 446 adversariella; 83,6 % på samma 1 540 | +6,3, inte +14,3 |\n\nTestningen visar vart skillnaden tar vägen. Den publicerade baslinjen inkluderar 446 adversariella frågor, där Haiku fick 46,2 %, och Honchos körning hade inga alls. Plastic Labs eget inlägg [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) säger ”Haiku alone scores 83.9%”, nära våra 83,6 %. Evals-sidan jämför helt enkelt två olika frågeuppsättningar.\n\nPå korta historiker är skälet att välja Honcho färre tokens, inte högre träffsäkerhet. [LoCoMo](https://arxiv.org/abs/2402.17753)-historiker på 16K till 26K tokens ryms i vilket 200K-fönster som helst, och [ConvoMem](https://arxiv.org/abs/2511.10523) fann att full kontext når 70–82 % under cirka 150 konversationer.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S är annorlunda: vid cirka 115K tokens per historik står sig försprånget på +27,8. En avgränsning. Körningarna använde en uppsättning från december 2025 med en Haiku 4.5-dialektik. Konfigurationen i open source-repot har `gpt-5.4-mini` som standard, men det är bara repots standardvärde; i produktion kör Plastic Labs andra modeller som inte är publicerade.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Varför väljer utvecklare Honcho?\n\nHoncho vinner på **användarmodellering**: det håller en löpande bild av vem någon är, och det minnet följer personen mellan hens agentverktyg.\n\nVectorize (som gör konkurrenten Hindsight) skrev i mars 2026 en [jämförelse av minnesleverantörer för Hermes](https://vectorize.io/articles/hermes-agent-memory-providers-compared) som kallar Honcho en beteendemodell av användaren, ”not just a fact store”. Varje skäl har en hake.\n\n| Skäl | Belägg | Haken |\n|---|---|---|\n| Det modellerar personen | ”Great on knowing who YOU are” ([r/hermesagent, maj 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` är ett live-anrop till en LLM, så varje fråga ger märkbar latens |\n| Ett minne över alla verktyg | Plugins för Claude Code, Codex, Cursor, OpenCode, OpenClaw och Hermes, plus en [MCP-server](/sv/blogg/basta-mcp-servrar-claude-code) med öppen källkod, hostad på `mcp.honcho.dev` eller självhostad | Bara text än så länge, med mycket begränsad OCR för dokument |\n| Träffsäkerhet i användartester | Ett test av sex leverantörer på Qwen3.5 4B: Honcho ”performed the best” ([r/hermesagent, aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Med pluginets standardinställningar ”almost 3 times the tokens of the next best performer” |\n| Integritet | Självhostare nämner det ([Elkim, apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (se nackdelar) |\n\nTokenbesparingarna är där marknadsföringen springer före. Startsidan utlovar 60–90 %, men [evals-sidan](https://honcho.dev/evals) listar 89 % på LongMemEval S, 52 % på LoCoMo och 16 % på BEAM 100K. En byggare som citeras på startsidan rapporterar 10–15 %.\n\n## Vem använder Honcho, och för vem är det?\n\n542 206 nedladdningar av Python-SDK:t under månaden fram till den 28 oktober 2026 visar att Honcho har riktiga användare, mestadels agentbyggare kring Hermes och kodagenter.\n\n```stats\ncaption: Adoptionssignaler, hämtade 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai-nedladdningar, senaste månaden\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk-nedladdningar, 27 sep till 26 okt\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub-stjärnor, 954 forkar\n    source: GitHub API\n```\n\nStartsidan märker sin logotypremsa ”Used by developers at”. Det betyder enskilda utvecklare på de här organisationerna, inte företagsövergripande avtal eller kundcase.\n\n| Grupp | Exempel från honcho.dev |\n|---|---|\n| Storföretag | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI-team | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Forskning | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Researchs [Hermes Agent](/sv/blogg/hermes-agent-v0-15) levereras med Honcho som minnesplugin (`hermes plugins install honcho`), och [Hermes Honcho-dokumentationen](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) listar fem verktyg, från `honcho_profile` till `honcho_conclude`.\n\nPopularitet är inte samsyn. En Hermes-omröstning på X med 138 svar ([okt 2026](https://x.com/HermesWatcher/status/2114492238659305561)) hade Markdown-anteckningar etta (27), Hindsight tvåa (25) och Honcho trea (22).\n\n- Passar bra: sällskapsagenter, handledare och coachande agenter\n- Passar bra: personliga kodagenter som delas mellan Claude Code, Codex och Cursor\n- Passar dåligt: dokument-RAG, återkallning i nästa tur, stängda forkar\n\n## Honchos för- och nackdelar: vad betalar du för träffsäkerheten?\n\nHonchos träffsäkerhet är verklig; priset är fördröjning, tokenoverhead, en tung självhostningsstack och AGPL, så räkna med alla fyra.\n\nSjälvhostning kräver Postgres med [pgvector](/sv/blogg/qdrant-vs-chroma-vs-pgvector-jamforelse), en deriver-worker och en LLM-modell med tool calling (standardvärden i repots konfiguration: `gpt-5.4-mini`, `text-embedding-3-small`). CLI:t startar API:et, deriver, Postgres och Redis; Docker Compose fungerar också.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # bearbeta små batcher direkt\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Fördelar: där Honcho förtjänar sin plats\n\n- Användarmodellering som utvecklare beskriver som att den vet vem du är\n- Det starkaste resultatet på långa historiker i vår omräkning: +27,8 på LongMemEval S\n- Öppen källkod, går att självhosta, med plugins för Claude Code, Codex, Cursor, Hermes och fler\n\n### Nackdelar: vad det kostar dig\n\n- Fördröjning. Utvecklare rapporterar ett dialektiskt `minimal`-spår på 9,1 s ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) och 2,16 s extra för varje Hermes-API-tur ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). Startsidans ”~200 ms” är ett påstående från leverantören om `context()`.\n- Frågekostnad. För 10 000 användare som lägger till 20K tokens i månaden blir inläsningen **$400**, men 30 frågor på nivån Low per användare blir **$3,000** (Minimal: $300). Frågenivån, inte inläsningen, avgör din Honcho-räkning.\n- Underhåll vid självhostning och inlåsning. API:et, deriver, Postgres, Redis och en LLM kör du själv. Att byta mellan moln och självhostning innebär att spela upp meddelandena igen, eftersom embeddings inte exporteras ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. En jämförelseartikel hävdar att självhostning tvingar dig att släppa appens källkod. Det överdriver: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) gäller när du ändrar Honcho och användare når det över ett nätverk. Mem0, Letta och cognee är Apache-2.0 och LangMem är MIT, så Honcho är det avvikande copyleft-fallet bland de dedikerade minneslagren. Inte juridisk rådgivning.\n\nKör snabbstarten på de $5 i kredit med en riktig konversationslogg innan du binder dig.\n\n## Vanliga frågor\n\n### Är Honcho memory gratis?\n\nDelvis. Molntjänsten ger $5 i kredit, plus $5 i månaden med kort, och startups som har tagit in under $5M kan få $1,000 i kredit. Självhostning har ingen licensavgift under AGPL-3.0, men du betalar dina egna LLM- och embedding-kostnader.\n\n### Kan jag använda Honcho i en SaaS med stängd källkod?\n\nJa, om din app anropar en omodifierad Honcho-server via dess API. Om du ändrar Honcho och serverar det över ett nätverk kräver AGPL §13 att du erbjuder källkoden till den ändrade Honcho-versionen. Din egen app förblir stängd. Inte juridisk rådgivning; fråga en jurist om du forkar.\n\n### Honcho jämfört med Mem0 eller Hindsight: vilket ska jag välja?\n\nVälj Mem0 (Apache-2.0) för snabbast start, Hindsight (MIT) för att spara tokens och Honcho för användarmodellering. En utvecklare rapporterar att Hindsight ”used far fewer tokens” på Hermes ([X, okt 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0:s blogg säger att Honcho saknar offentliga benchmarks, men Honcho har publicerat 21 råa resultatfiler sedan 2025-12-19. Se [hela rankningen](/sv/blogg/basta-ai-agentminnesverktyg).\n\n```references\ntitle: Referenser\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min läsning","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agentminne","honcho memory recension"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory med LongMemEval S-poängen 90,4 %, reproducerad i vår omräkning, över en svag graf av minnesnoder","seo":{"metaTitle":"Honcho memory: för- och nackdelar, pris och omräknad benchmark","metaDescription":"Är Honcho memory värt det? Vår testning reproducerade benchmarkpoängen 90,4 %. Här är för- och nackdelarna, det verkliga priset och vem som använder det 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:08.797Z","createdAt":"2026-10-28T16:06:33.831Z","_status":"published"},{"id":8825,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory-test: 90.4% holder i vår omscoring, pluss fordeler og ulemper","slug":"honcho-memory-review","language":"no","excerpt":"Vi telte opp Honchos rå benchmark-filer på nytt: 90.4 % på LongMemEval S gjentar seg eksakt, og LoCoMo-forspranget over Haiku alene er 6.3 poeng med lik telling. Her er fordeler, ulemper, reelle priser og hvem som faktisk bruker det.","body":"# Honcho Memory-test: 90.4% holder i vår omscoring, pluss fordeler og ulemper\n\n**Honcho memory**, Plastic Labs' AGPL-3.0-lisensierte [minnelag for AI-agenter](/no/blogg/guide-ai-agent-hukommelse), hevder 90.4 % på LongMemEval S. Testingen vår 28. oktober 2026 telte opp de rå resultatfilene på nytt og endte på de samme 452 av 500. På LoCoMo, der begge sider svarer på de samme 1,540 spørsmålene, er Honchos forsprang over vanlig Claude Haiku 4.5 på **6.3 poeng**, ikke de publiserte 14.3.\n\nGodt minne. Mindre forsprang. Reelle kompromisser.\n\n## Er Honcho Memory verdt å bruke? Dommen i én tabell\n\nBruk Honcho når agenten din må modellere en person over måneder; hopp over det for dokument-RAG, øyeblikkelig gjenkalling eller en closed source-fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) er det eneste **AGPL-3.0**-alternativet blant de dedikerte minnelagene (Mem0, Letta og cognee er Apache-2.0, LangMem er MIT), og skyen deres fakturerer resonnering per spørring i tillegg til innlesing.\n\n| Spørsmål | Svar |\n|---|---|\n| Pris, managed (sjekket 2026-10-28) | $2 per 1M innleste tokens; $0.001 til $0.50 per resonneringsspørring; `context()` ubegrenset; $5 gratis kreditt |\n| Selvhosting krever | Postgres med pgvector, en deriver-worker, en LLM-nøkkel med tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (selvrapportert; lik-for-lik-løft +27.8 og +6.3) |\n| Best for | Agenter som modellerer én person over tid |\n| Velg noe annet til | Dokument-RAG, gjenkalling i neste tur, closed source-forks ([vår rangerte liste over minneverktøy](/no/blogg/beste-ai-agentminneverktoy-rangert) plasserer Honcho som nr. 3) |\n\nEldre omtaler siterer fortsatt $100 i gratis kreditt. Dokumentasjonen sier nå $5, pluss $5 i måneden med kort.\n\n## Hvordan fungerer Honcho Memory?\n\nAppen din skriver meldinger mellom peers, og en bakgrunnsworker gjør dem om til konklusjoner som du kan spørre om på vanlig språk eller hente ut som kontekst.\n\nEn peer er en hvilken som helst deltaker, bruker eller agent. Quickstart for v3 i [Honcho-dokumentasjonen](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) viser hele flyten (kildekoden ligger på [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` svarer på spørsmål på vanlig språk. [Hybrid BM25 + vektorsøk](/no/blogg/hybridsok-bm25-vs-vektor) finner meldinger og konklusjoner, som er Honchos utledede fakta. `session.context(summary=True, tokens=10_000)` returnerer [kontekst med tokenbudsjett](/no/blogg/context-engineering-guide-no) til en prompt.\n\nResonneringen er asynkron. Et nytt faktum dukker opp etter at deriveren har kjørt, ikke ved neste lesing; `representation`-endepunktet i README-en er veien med lav latens.\n\n## Holder Honchos 89.9% på LoCoMo? Vi scoret de rå filene på nytt\n\n89.9% og 90.4% lar seg begge gjenskape fra Plastic Labs' rå filer; på LoCoMo er derimot forspranget over Haiku alene 6.3 poeng når tellingen er lik.\n\n28. oktober 2026 telte vi opp tre resultatfiler fra [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (kjørings-mappen `a1d689b`, oppkalt etter Honcho-committen som ble testet). Kolonnen «Publisert» er selvrapportert på [honcho.dev/evals](https://honcho.dev/evals).\n\n| Kjøring | Publisert | Vår opptelling | Lik-for-lik-løft |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 spørsmål | n/a |\n| LoCoMo, Haiku 4.5 alene | 75.6% | 75.4% med 446 adversarial; 83.6% på de samme 1,540 | +6.3, ikke +14.3 |\n\nTestingen viser hvor forskjellen blir av. Den publiserte baselinen inkluderer 446 adversarial-spørsmål, der Haiku fikk 46.2 %, og Honchos kjøring hadde ingen. Plastic Labs' eget innlegg [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) sier «Haiku alone scores 83.9%», nær våre 83.6 %. Evals-siden sammenligner rett og slett to ulike spørsmålssett.\n\nPå korte historikker er grunnen til å velge Honcho færre tokens, ikke høyere treffsikkerhet. [LoCoMo](https://arxiv.org/abs/2402.17753)-historikker på 16K til 26K tokens får plass i ethvert kontekstvindu på 200K, og [ConvoMem](https://arxiv.org/abs/2511.10523) fant at full kontekst når 70-82 % under omtrent 150 samtaler.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S er annerledes: med omtrent 115K tokens per historikk holder forspranget på +27.8. En merknad om omfang: kjøringene brukte et oppsett fra desember 2025 med en Haiku 4.5-dialektikk. Konfigurasjonen i open source-repoet har `gpt-5.4-mini` som standard, men det er bare repoets standardverdi; i produksjon kjører Plastic Labs andre modeller som ikke er publisert.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Hvorfor velger utviklere Honcho?\n\nHoncho vinner på **brukermodellering**: det holder et løpende bilde av hvem noen er, og det minnet følger dem på tvers av agentverktøyene deres.\n\nVectorize (som lager konkurrenten Hindsight) skrev i mars 2026 en [sammenligning av minneleverandører for Hermes](https://vectorize.io/articles/hermes-agent-memory-providers-compared) som kaller det en atferdsmodell av brukeren, «not just a fact store». Hver grunn har en hake.\n\n| Grunn | Belegg | Haken |\n|---|---|---|\n| Det modellerer personen | «Great on knowing who YOU are» ([r/hermesagent, mai 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` er et live LLM-kall, så hvert spørsmål gir merkbar latens |\n| Ett minne på tvers av verktøy | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw og Hermes, pluss en [MCP-server](/no/blogg/beste-mcp-servere-for-claude-code-2026) med åpen kildekode, hostet på `mcp.honcho.dev` eller selvhostet | Foreløpig bare tekst, med svært begrenset OCR for dokumenter |\n| Treffsikkerhet i brukertester | En bake-off med seks leverandører på Qwen3.5 4B: Honcho «performed the best» ([r/hermesagent, aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Med pluginens standardinnstillinger «almost 3 times the tokens of the next best performer» |\n| Personvern | Selvhostere trekker det frem ([Elkim, apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (se ulemper) |\n\nTokenbesparelsene er der markedsføringen løper foran. Forsiden reklamerer med 60-90 %, men [evals-siden](https://honcho.dev/evals) oppgir 89 % på LongMemEval S, 52 % på LoCoMo og 16 % på BEAM 100K. En bygger som siteres på forsiden melder om 10-15 %.\n\n## Hvem bruker Honcho, og hvem er det for?\n\n542,206 nedlastinger av Python-SDK-en i måneden frem til 28. oktober 2026 viser at Honcho har ekte brukere, mest agentbyggere rundt Hermes og kodeagenter.\n\n```stats\ncaption: Tegn på bruk, hentet 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai-nedlastinger, siste måned\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk-nedlastinger, 27. sep til 26. okt\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub-stjerner, 954 forks\n    source: GitHub API\n```\n\nForsiden merker logostripen sin «Used by developers at». Det betyr enkeltutviklere hos disse organisasjonene, ikke selskapsomfattende avtaler eller kundecaser.\n\n| Gruppe | Eksempler fra honcho.dev |\n|---|---|\n| Storselskaper | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI-team | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Forskning | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Researchs [Hermes Agent](/no/blogg/hermes-agent-v0-15-norsk) leveres med Honcho som minne-plugin (`hermes plugins install honcho`), og [Hermes Honcho-dokumentasjonen](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) lister fem verktøy, fra `honcho_profile` til `honcho_conclude`.\n\nPopularitet er ikke det samme som enighet. En Hermes-avstemning på X med 138 svar ([okt 2026](https://x.com/HermesWatcher/status/2114492238659305561)) satte Markdown-notater først (27), Hindsight på andreplass (25) og Honcho på tredjeplass (22).\n\n- Passer godt: følgesvenner, veiledere og coaching-agenter\n- Passer godt: personlige kodeagenter som deles mellom Claude Code, Codex og Cursor\n- Passer dårlig: dokument-RAG, gjenkalling i neste tur, closed source-forks\n\n## Honcho: fordeler og ulemper. Hva betaler du for treffsikkerheten?\n\nHonchos treffsikkerhet er reell; prisen er forsinkelse, token-overhead, en tung selvhostingstack og AGPL-lisensen, så sett av rom til alle fire.\n\nSelvhosting krever Postgres med [pgvector](/no/blogg/qdrant-vs-chroma-vs-pgvector-sammenligning), en deriver-worker og en LLM med tool calling (standardverdier i repo-konfigurasjonen: `gpt-5.4-mini`, `text-embedding-3-small`). CLI-en starter API-et, deriveren, Postgres og Redis; Docker Compose fungerer også.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # behandle små batcher med en gang\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Fordeler: der Honcho fortjener plassen sin\n\n- Brukermodellering som utviklere beskriver som at det vet hvem du er\n- Det sterkeste resultatet på lange historikker i vår opptelling: +27.8 på LongMemEval S\n- Open source, kan selvhostes, med plugins for Claude Code, Codex, Cursor, Hermes og flere\n\n### Ulemper: hva det koster deg\n\n- Forsinkelse. Utviklere melder om et dialektikk-spor på 9.1 s i `minimal`-modus ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) og 2.16 s lagt til hver Hermes API-tur ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). «~200 ms» på forsiden er et leverandørpåstand om `context()`.\n- Spørringskostnad. For 10,000 brukere som legger til 20K tokens i måneden blir innlesing **$400**, men 30 Low-nivå-spørringer hver blir **$3,000** (Minimal: $300). Spørringsnivået, ikke innlesing, avgjør Honcho-regningen din.\n- Vedlikehold ved selvhosting og innlåsing. API-et, deriveren, Postgres, Redis og en LLM kjører du selv. Å bytte mellom sky og selvhosting betyr å spille av meldingene på nytt, fordi embeddings ikke eksporteres ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. En sammenligningsartikkel hevder at selvhosting tvinger deg til å utgi appens kildekode. Det er en overdrivelse: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) gjelder når du endrer Honcho og brukere når det over et nettverk. Mem0, Letta og cognee er Apache-2.0 og LangMem er MIT, så Honcho er copyleft-uteliggeren blant de dedikerte minnelagene. Ikke juridisk rådgivning.\n\nKjør quickstart på $5-kreditten med én ekte samtalelogg før du binder deg.\n\n## Ofte stilte spørsmål\n\n### Er Honcho memory gratis?\n\nDelvis. Skyen gir $5 i kreditt, pluss $5 i måneden med kort, og oppstartsselskaper som har hentet under $5M kan få $1,000 i kreditt. Selvhosting har ingen lisensavgift under AGPL-3.0, men du betaler for dine egne LLM- og embedding-regninger.\n\n### Kan jeg bruke Honcho i en closed source-SaaS?\n\nJa, hvis appen din kaller en uendret Honcho-server gjennom API-et. Hvis du endrer Honcho og serverer det over et nettverk, krever AGPL §13 at du tilbyr kildekoden til den endrede Honcho-versjonen. Din egen app forblir lukket. Ikke juridisk rådgivning; spør en jurist hvis du forker.\n\n### Honcho vs Mem0 eller Hindsight: hva bør jeg velge?\n\nVelg Mem0 (Apache-2.0) for raskest start, Hindsight (MIT) for å spare tokens, og Honcho for brukermodellering. En utvikler melder at Hindsight «used far fewer tokens» på Hermes ([X, okt 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0-bloggen sier at Honcho mangler offentlige benchmarks, men det har publisert 21 rå resultatfiler siden 2025-12-19. Se [hele rangeringen](/no/blogg/beste-ai-agentminneverktoy-rangert).\n\n```references\ntitle: Referanser\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min lesetid","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory: LongMemEval S-score på 90.4 %, gjentatt i vår omscoring, over en svak graf av minnenoder","seo":{"metaTitle":"Honcho Memory: test, fordeler, ulemper og ny benchmark","metaDescription":"Er Honcho memory verdt det? Testingen vår gjentok benchmark-scoren på 90.4 %. Her er fordeler, ulemper, reelle priser og hvem som bruker det i 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:08.461Z","createdAt":"2026-10-28T16:06:33.419Z","_status":"published"},{"id":8824,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory review: 90,4% houdt stand in onze herberekening, plus voor- en nadelen","slug":"honcho-memory-review","language":"nl","excerpt":"We telden de ruwe benchmarkbestanden van Honcho opnieuw na: de score van 90,4% op LongMemEval S klopt exact, en de voorsprong op LoCoMo ten opzichte van Haiku alleen is 6,3 punten op een eerlijke vergelijking. Dit zijn de voor- en nadelen, de echte prijzen en wie het gebruikt.","body":"# Honcho Memory review: 90,4% houdt stand in onze herberekening, plus voor- en nadelen\n\n**Honcho Memory**, de AGPL-3.0 [geheugenlaag voor AI-agents](/nl/blog/ai-agent-geheugen-gids) van Plastic Labs, claimt 90,4% op LongMemEval S. Onze hertelling van de ruwe resultaatbestanden op 28 oktober 2026 kwam op hetzelfde aantal uit: 452 van 500. Op LoCoMo, waar beide kanten dezelfde 1.540 vragen beantwoorden, is de voorsprong van Honcho op gewone Claude Haiku 4.5 **6,3 punten**, niet de gepubliceerde 14,3.\n\nGoed geheugen. Kleinere voorsprong. Echte afwegingen.\n\n## Is Honcho Memory het gebruiken waard? Het oordeel in één tabel\n\nGebruik Honcho als je agent een persoon maandenlang moet modelleren; sla het over voor document-RAG, directe recall of een closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is de enige **AGPL-3.0**-optie onder de speciale geheugenlagen (Mem0, Letta en cognee zijn Apache-2.0, LangMem is MIT), en de cloud rekent naast ingestie ook redeneren per query af.\n\n| Vraag | Antwoord |\n|---|---|\n| Prijs managed (gecontroleerd 2026-10-28) | $2 per 1M geïngesteerde tokens; $0.001 tot $0.50 per redeneerquery; `context()` onbeperkt; $5 gratis tegoed |\n| Self-hosten vereist | Postgres met pgvector, een deriver worker, een LLM-sleutel met tool calling |\n| Benchmarks | LongMemEval S 90,4%, LoCoMo 89,9% (zelf gerapporteerd; voorsprong op eerlijke vergelijking +27,8 en +6,3) |\n| Het best voor | Agents die één persoon in de loop van de tijd modelleren |\n| Kies iets anders voor | Document-RAG, recall in de volgende beurt, closed-source forks ([ons overzicht van geheugentools](/nl/blog/beste-ai-agent-geheugentools) zet Honcho op #3) |\n\nOudere reviews noemen nog $100 gratis tegoed. In de docs staat nu $5, plus $5 per maand met een creditcard.\n\n## Hoe werkt Honcho Memory?\n\nJe app schrijft berichten tussen peers, en een achtergrondworker maakt daar conclusies van die je in gewone taal kunt bevragen of als context kunt ophalen.\n\nEen peer is elke deelnemer, gebruiker of agent. De v3-quickstart in de [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) toont de hele flow (broncode op [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` beantwoordt vragen in gewone taal. [Hybride BM25 + vectorzoeken](/nl/blog/hybride-zoeken-bm25-vs-vector) vindt berichten en conclusies, de afgeleide feiten van Honcho. `session.context(summary=True, tokens=10_000)` levert [context binnen een tokenbudget](/nl/blog/context-engineering-gids) voor een prompt.\n\nHet redeneren gebeurt asynchroon. Een nieuw feit verschijnt nadat de deriver gedraaid heeft, niet bij de eerstvolgende leesactie; het `representation`-endpoint uit de README is de route met lage latency.\n\n## Houdt de LoCoMo-score van 89,9% stand? We hebben de ruwe bestanden opnieuw gescoord\n\n89,9% en 90,4% komen allebei uit de ruwe bestanden van Plastic Labs; op LoCoMo is de voorsprong op Haiku alleen bij een eerlijke vergelijking maar 6,3 punten.\n\nOp 28 oktober 2026 telden we drie resultaatbestanden uit [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) opnieuw na (runmap `a1d689b`, vernoemd naar de geteste Honcho-commit). De gepubliceerde kolom is zelf gerapporteerd op [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Gepubliceerd | Onze hertelling | Voorsprong op eerlijke vergelijking |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90,4% (baseline 62,6%) | 452/500 | +27,8 |\n| LoCoMo, Honcho | 89,9% | 89,9%, 1.540 vragen | n.v.t. |\n| LoCoMo, Haiku 4.5 alleen | 75,6% | 75,4% met 446 adversarial; 83,6% op dezelfde 1.540 | +6,3, niet +14,3 |\n\nDe cijfers laten zien waar het verschil blijft hangen. De gepubliceerde baseline bevat 446 adversarial vragen, waarop Haiku 46,2% haalde, en de run van Honcho had er geen. Het eigen artikel van Plastic Labs, [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho), zegt \"Haiku alone scores 83.9%\", dicht bij onze 83,6%. De evals-pagina vergelijkt simpelweg twee vragensets.\n\nBij korte geschiedenissen is de reden om Honcho te kiezen dus minder tokens, niet hogere nauwkeurigheid. [LoCoMo](https://arxiv.org/abs/2402.17753)-geschiedenissen van 16K tot 26K tokens passen in elk venster van 200K, en [ConvoMem](https://arxiv.org/abs/2511.10523) vond dat volledige context 70-82% haalt onder zo'n 150 gesprekken.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S ligt anders: bij ongeveer 115K tokens per geschiedenis houdt de voorsprong van +27,8 stand. Eén kanttekening: deze runs gebruikten een setup van december 2025 met een Haiku 4.5-dialectic. De config in de open-source repo gebruikt standaard `gpt-5.4-mini`, maar dat is alleen de repo-default; Plastic Labs draait in productie andere, niet-gepubliceerde modellen.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Waarom kiezen developers voor Honcho?\n\nHoncho wint op **user modeling**: het houdt een lopend beeld bij van wie iemand is, en dat geheugen volgt die persoon door al zijn agent-tools.\n\nVectorize (maker van het concurrerende Hindsight) schreef in maart 2026 een [vergelijking van Hermes-geheugenproviders](https://vectorize.io/articles/hermes-agent-memory-providers-compared) die Honcho een gedragsmodel van de gebruiker noemt, \"not just a fact store\". Elke reden heeft een addertje.\n\n| Reden | Bewijs | Addertje |\n|---|---|---|\n| Het modelleert de persoon | \"Great on knowing who YOU are\" ([r/hermesagent, mei 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is een live LLM-call, dus elke vraag kost merkbaar latency |\n| Eén geheugen over tools heen | Plugins voor Claude Code, Codex, Cursor, OpenCode, OpenClaw en Hermes, plus een open-source [MCP-server](/nl/blog/beste-mcp-servers-claude-code), gehost op `mcp.honcho.dev` of zelf te hosten | Voorlopig alleen tekst, met zeer beperkte OCR voor documenten |\n| Nauwkeurigheid in gebruikerstests | Een bake-off van zes providers op Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Met de standaardinstellingen van de plugin \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters noemen het ([Elkim, apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (zie nadelen) |\n\nBij tokenbesparing loopt de marketing voor op de feiten. De homepage adverteert met 60-90%, maar de [evals-pagina](https://honcho.dev/evals) noemt 89% op LongMemEval S, 52% op LoCoMo en 16% op BEAM 100K. Een op de homepage geciteerde bouwer meldt 10-15%.\n\n## Wie gebruikt Honcho, en voor wie is het?\n\n542.206 downloads van de Python-SDK in de maand tot 28 oktober 2026 laten zien dat Honcho echte gebruikers heeft, vooral agentbouwers rond Hermes en coding agents.\n\n```stats\ncaption: Adoptiesignalen, opgehaald op 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, afgelopen maand\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, 27 sep t/m 26 okt\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub-sterren, 954 forks\n    source: GitHub API\n```\n\nDe homepage noemt de logostrip \"Used by developers at\". Dat betekent individuele developers bij deze organisaties, geen bedrijfsbrede contracten of casestudy's.\n\n| Groep | Voorbeelden van honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI-teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Onderzoek | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\n[Hermes Agent](/nl/blog/hermes-agent-v0-15) van Nous Research levert Honcho als geheugenplugin (`hermes plugins install honcho`), en de [Hermes Honcho-docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) noemen vijf tools, van `honcho_profile` tot `honcho_conclude`.\n\nPopulair is niet hetzelfde als consensus. In een Hermes-poll op X met 138 antwoorden ([okt 2026](https://x.com/HermesWatcher/status/2114492238659305561)) stonden Markdown-notities op één (27), Hindsight op twee (25) en Honcho op drie (22).\n\n- Goede match: companions, tutors en coachingagents\n- Goede match: persoonlijke coding agents die Claude Code, Codex en Cursor delen\n- Slechte match: document-RAG, recall in de volgende beurt, closed-source forks\n\n## Voor- en nadelen van Honcho: wat betaal je voor de nauwkeurigheid?\n\nDe nauwkeurigheid van Honcho is echt; je betaalt met vertraging, tokenoverhead, een zware self-hostingstack en de AGPL, dus reken met alle vier.\n\nSelf-hosten vraagt Postgres met [pgvector](/nl/blog/qdrant-vs-chroma-vs-pgvector-vergelijking), een deriver worker en een LLM met tool calling (standaardwaarden in de repo-config: `gpt-5.4-mini`, `text-embedding-3-small`). De CLI start de API, de deriver, Postgres en Redis; Docker Compose werkt ook.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # kleine batches direct verwerken\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Voordelen: waar Honcho zijn plek verdient\n\n- User modeling waarvan developers zeggen dat het weet wie je bent\n- Het sterkste resultaat bij lange geschiedenissen in onze hertelling: +27,8 op LongMemEval S\n- Open source, zelf te hosten, met plugins voor Claude Code, Codex, Cursor, Hermes en meer\n\n### Nadelen: wat het je kost\n\n- Vertraging. Developers melden een dialectic-trace van 9,1 s op `minimal` ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) en 2,16 s extra bij elke Hermes-API-beurt ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). De \"~200 ms\" op de homepage is een claim van de leverancier over `context()`.\n- Querykosten. Bij 10.000 gebruikers die elk 20K tokens per maand toevoegen, kost ingestie **$400**, maar 30 Low-tier queries per gebruiker kosten **$3,000** (Minimal: $300). De querytier, niet de ingestie, bepaalt je Honcho-rekening.\n- Onderhoud bij self-hosten en lock-in. De API, de deriver, Postgres, Redis en een LLM draai je zelf. Wisselen tussen cloud en self-hosten betekent berichten opnieuw afspelen, want embeddings worden niet geëxporteerd ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. Een vergelijkend artikel zegt dat self-hosten je dwingt de broncode van je app vrij te geven. Dat is overdreven: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) geldt wanneer je Honcho aanpast en gebruikers het via een netwerk bereiken. Mem0, Letta en cognee zijn Apache-2.0 en LangMem is MIT, dus Honcho is de copyleft-uitzondering onder de speciale geheugenlagen. Geen juridisch advies.\n\nDraai de quickstart op het tegoed van $5 met één echt gesprekslog voordat je je vastlegt.\n\n## Veelgestelde vragen\n\n### Is Honcho Memory gratis?\n\nGedeeltelijk. De cloud geeft $5 tegoed, plus $5 per maand met een creditcard, en startups die minder dan $5M hebben opgehaald kunnen $1,000 aan tegoed krijgen. Self-hosten kost geen licentie onder AGPL-3.0, maar je betaalt je eigen LLM- en embeddingrekeningen.\n\n### Kan ik Honcho gebruiken in een closed-source SaaS?\n\nJa, als je app een ongewijzigde Honcho-server via de API aanroept. Pas je Honcho aan en bied je het via een netwerk aan, dan vereist AGPL §13 dat je die aangepaste Honcho-broncode aanbiedt. Je eigen app blijft gesloten. Geen juridisch advies; vraag een jurist als je forkt.\n\n### Honcho vs Mem0 of Hindsight: wat kies ik?\n\nKies Mem0 (Apache-2.0) voor de snelste start, Hindsight (MIT) om tokens te besparen en Honcho voor user modeling. Een developer meldt dat Hindsight op Hermes \"used far fewer tokens\" ([X, okt 2026](https://x.com/StillYazeed/status/2115014740145512772)). De blog van Mem0 zegt dat Honcho geen publieke benchmarks heeft, maar sinds 2025-12-19 zijn er 21 ruwe resultaatbestanden gepubliceerd. Zie [het volledige overzicht](/nl/blog/beste-ai-agent-geheugentools).\n\n```references\ntitle: Bronnen\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min lezen","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho Memory LongMemEval S-score van 90,4%, gereproduceerd in onze hertelling, boven een vaag netwerk van geheugenknopen","seo":{"metaTitle":"Honcho Memory review: voor- en nadelen + benchmark-check","metaDescription":"Is Honcho Memory het waard? Onze hertelling reproduceerde de benchmarkscore van 90,4%. Voor- en nadelen, echte prijzen en wie het gebruikt in 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:08.113Z","createdAt":"2026-10-28T16:06:32.501Z","_status":"published"},{"id":8823,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho memory: recensione, il 90,4% regge al nostro nuovo conteggio (pro e contro)","slug":"honcho-memory-recensione","language":"it","excerpt":"Abbiamo ricontato i file grezzi dei benchmark di Honcho: il 90,4% su LongMemEval S si riproduce esattamente, mentre su LoCoMo il vantaggio su Haiku da solo è di 6,3 punti a parità di domande. Pro, contro, prezzi reali e chi lo usa davvero.","body":"# Honcho memory: recensione, il 90,4% regge al nostro nuovo conteggio (pro e contro)\n\n**Honcho memory**, il [livello di memoria per agenti IA](/it/blog/guida-memoria-agenti-ia) di Plastic Labs con licenza AGPL-3.0, dichiara il 90,4% su LongMemEval S. Il nostro test del 28 ottobre 2026 ha ricontato i suoi file di risultati grezzi e ha ottenuto lo stesso 452 su 500. Su LoCoMo, con entrambi i lati che rispondono alle stesse 1.540 domande, il vantaggio di Honcho su Claude Haiku 4.5 semplice è di **6,3 punti**, non i 14,3 pubblicati.\n\nMemoria buona. Vantaggio più piccolo. Compromessi reali.\n\n## Honcho memory vale la pena? Il verdetto in una tabella\n\nUsa Honcho quando il tuo agente deve modellare una persona nell'arco di mesi; lascialo da parte per RAG su documenti, richiamo immediato o fork closed source.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) è l'unica opzione **AGPL-3.0** tra i livelli di memoria dedicati (Mem0, Letta e cognee sono Apache-2.0, LangMem è MIT) e il suo cloud fattura il ragionamento a query, oltre all'ingestione.\n\n| Domanda | Risposta |\n|---|---|\n| Prezzi gestiti (verificati il 2026-10-28) | $2 per 1M di token ingeriti; da $0.001 a $0.50 per query di ragionamento; `context()` illimitato; $5 di credito gratuito |\n| Per il self-hosted servono | Postgres con pgvector, un worker deriver, una chiave LLM con tool calling |\n| Benchmark | LongMemEval S 90,4%, LoCoMo 89,9% (dati autodichiarati; vantaggio a parità di condizioni +27,8 e +6,3) |\n| Ideale per | Agenti che modellano una singola persona nel tempo |\n| Scegli altro per | RAG su documenti, richiamo al turno successivo, fork closed source ([la nostra classifica degli strumenti di memoria](/it/blog/migliori-strumenti-memoria-agenti-ia) mette Honcho al #3) |\n\nLe recensioni più vecchie citano ancora $100 di credito gratuito. La documentazione ora parla di $5, più $5 al mese con una carta.\n\n## Come funziona Honcho memory?\n\nLa tua app scrive messaggi tra peer, e un worker in background li trasforma in conclusioni che puoi interrogare in linguaggio naturale o recuperare come contesto.\n\nUn peer è qualsiasi partecipante, utente o agente. Il quickstart v3 nella [documentazione di Honcho](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) mostra l'intero flusso (codice sorgente su [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` risponde a domande in linguaggio naturale. La [ricerca ibrida BM25 + vettoriale](/it/blog/ricerca-ibrida-bm25-vs-vettoriale) trova messaggi e conclusioni, cioè i fatti derivati da Honcho. `session.context(summary=True, tokens=10_000)` restituisce un [contesto con budget di token](/it/blog/guida-context-engineering) da inserire nel prompt.\n\nIl ragionamento è asincrono. Un nuovo fatto compare dopo l'esecuzione del deriver, non alla lettura successiva; l'endpoint `representation` del README è la via a bassa latenza.\n\n## Il 89,9% di Honcho su LoCoMo regge? Abbiamo ricontato i file grezzi\n\nSia l'89,9% sia il 90,4% si riproducono dai file grezzi di Plastic Labs; su LoCoMo, però, il vantaggio a parità di condizioni su Haiku da solo è di 6,3 punti.\n\nIl 28 ottobre 2026 abbiamo ricontato tre file di risultati da [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (cartella di esecuzione `a1d689b`, che prende il nome dal commit di Honcho testato). La colonna dei valori pubblicati è autodichiarata su [honcho.dev/evals](https://honcho.dev/evals).\n\n| Esecuzione | Pubblicato | Il nostro conteggio | Vantaggio a parità di condizioni |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90,4% (baseline 62,6%) | 452/500 | +27,8 |\n| LoCoMo, Honcho | 89,9% | 89,9%, 1.540 domande | n/d |\n| LoCoMo, solo Haiku 4.5 | 75,6% | 75,4% con 446 avversariali; 83,6% sulle stesse 1.540 | +6,3, non +14,3 |\n\nIl test mostra dove finisce la differenza. La baseline pubblicata include 446 domande avversariali, su cui Haiku ha ottenuto il 46,2%, mentre l'esecuzione di Honcho non ne conteneva nessuna. Lo stesso post di Plastic Labs, [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho), scrive «Haiku alone scores 83.9%», vicino al nostro 83,6%. La pagina evals confronta semplicemente due insiemi di domande diversi.\n\nSulle cronologie brevi, il motivo per scegliere Honcho è l'uso di meno token, non una maggiore accuratezza. Le cronologie di [LoCoMo](https://arxiv.org/abs/2402.17753), da 16K a 26K token, stanno in qualsiasi finestra da 200K, e [ConvoMem](https://arxiv.org/abs/2511.10523) ha rilevato che il contesto completo raggiunge il 70-82% sotto le 150 conversazioni circa.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S è diverso: a circa 115K token per cronologia, il vantaggio di +27,8 regge. Una precisazione sul perimetro. Queste esecuzioni usavano una configurazione di dicembre 2025 con un dialectic basato su Haiku 4.5. La configurazione del repo open source usa `gpt-5.4-mini` come default, ma è solo il valore del repo: in produzione Plastic Labs usa altri modelli, non pubblicati.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Perché gli sviluppatori scelgono Honcho?\n\nHoncho vince sulla **modellazione dell'utente**. Tiene un quadro aggiornato di chi è una persona, e quella memoria la segue tra i suoi strumenti di agenti.\n\nVectorize (l'azienda dietro Hindsight, concorrente di Honcho) ha scritto a marzo 2026 un [confronto dei provider di memoria per Hermes](https://vectorize.io/articles/hermes-agent-memory-providers-compared) che lo definisce un modello comportamentale dell'utente, «not just a fact store». Ogni motivo ha il suo problema.\n\n| Motivo | Evidenza | Il problema |\n|---|---|---|\n| Modella la persona | «Great on knowing who YOU are» ([r/hermesagent, maggio 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` è una chiamata LLM dal vivo, quindi ogni domanda aggiunge latenza reale |\n| Una sola memoria tra più strumenti | Plugin per Claude Code, Codex, Cursor, OpenCode, OpenClaw e Hermes, più un [server MCP](/it/blog/server-mcp-claude-code) open source, ospitato su `mcp.honcho.dev` o self-hosted | Per ora solo testo, con OCR molto limitato per i documenti |\n| Accuratezza nei test degli utenti | Un confronto tra sei provider su Qwen3.5 4B: Honcho «performed the best» ([r/hermesagent, ago 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Con le impostazioni predefinite del plugin, «almost 3 times the tokens of the next best performer» |\n| Privacy | Chi lo ospita in proprio la cita ([Elkim, apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (vedi i contro) |\n\nSui risparmi di token il marketing corre più della realtà. La homepage promette il 60-90%, ma la [pagina evals](https://honcho.dev/evals) riporta l'89% su LongMemEval S, il 52% su LoCoMo e il 16% su BEAM 100K. Un builder citato nella homepage parla del 10-15%.\n\n## Chi usa Honcho e per chi è pensato?\n\n542.206 download dell'SDK Python nel mese fino al 28 ottobre 2026 dicono che Honcho ha utenti veri, soprattutto chi costruisce agenti attorno a Hermes e ai coding agent.\n\n```stats\ncaption: Segnali di adozione, rilevati il 2026-10-28.\nitems:\n  - value: 542206\n    label: download PyPI di honcho-ai, ultimo mese\n    source: pypistats.org\n  - value: 101791\n    label: download npm di @honcho-ai/sdk, dal 27 set al 26 ott\n    source: api.npmjs.org\n  - value: 7803\n    label: stelle su GitHub, 954 fork\n    source: GitHub API\n```\n\nLa homepage intitola la fascia dei loghi «Used by developers at». Significa singoli sviluppatori di queste organizzazioni, non contratti aziendali né casi di studio.\n\n| Gruppo | Esempi da honcho.dev |\n|---|---|\n| Grandi aziende | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| Team IA | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Ricerca | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\n[Hermes Agent](/it/blog/hermes-agent-v0-15) di Nous Research include Honcho come plugin di memoria (`hermes plugins install honcho`), e la [documentazione Hermes su Honcho](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) elenca cinque strumenti, da `honcho_profile` a `honcho_conclude`.\n\nLa popolarità non è consenso. Un sondaggio su X con 138 risposte tra utenti Hermes ([ott 2026](https://x.com/HermesWatcher/status/2114492238659305561)) ha messo al primo posto le note in Markdown (27), al secondo Hindsight (25) e al terzo Honcho (22).\n\n- Adatto a: companion, tutor e agenti di coaching\n- Adatto a: coding agent personali condivisi tra Claude Code, Codex e Cursor\n- Poco adatto a: RAG su documenti, richiamo al turno successivo, fork closed source\n\n## Pro e contro di Honcho: cosa dai in cambio dell'accuratezza?\n\nL'accuratezza di Honcho è reale; il prezzo sono latenza, overhead di token, uno stack self-hosted pesante e l'AGPL, quindi mettili tutti e quattro a budget.\n\nIl self-hosted richiede Postgres con [pgvector](/it/blog/qdrant-vs-chroma-vs-pgvector-confronto), un worker deriver e un LLM con tool calling (default della configurazione del repo: `gpt-5.4-mini`, `text-embedding-3-small`). La CLI avvia API, deriver, Postgres e Redis; funziona anche Docker Compose.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # elabora subito i batch piccoli\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pro: dove Honcho si guadagna il posto\n\n- Una modellazione dell'utente che gli sviluppatori descrivono come «sa chi sei»\n- Il risultato migliore sulle cronologie lunghe nel nostro conteggio: +27,8 su LongMemEval S\n- Open source, installabile in self-hosted, con plugin per Claude Code, Codex, Cursor, Hermes e altri\n\n### Contro: cosa ti costa\n\n- Latenza. Gli sviluppatori segnalano una traccia dialectic `minimal` di 9,1 s ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) e 2,16 s aggiunti a ogni turno API di Hermes ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). I «~200 ms» della homepage sono un'affermazione del fornitore su `context()`.\n- Costo delle query. Con 10.000 utenti che aggiungono 20K token al mese, l'ingestione costa **$400**, ma 30 query di livello Low ciascuno costano **$3,000** (Minimal: $300). Il livello delle query, non l'ingestione, decide la tua fattura Honcho.\n- Manutenzione del self-hosted e lock-in. API, deriver, Postgres, Redis e un LLM li gestisci tu. Passare dal cloud al self-hosted (o viceversa) significa rigiocare i messaggi, perché gli embedding non si esportano ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. Un articolo di confronto sostiene che il self-hosting ti obbliga a rilasciare il sorgente della tua app. È una forzatura: la [sezione 13 dell'AGPL](https://www.gnu.org/licenses/agpl-3.0.html) scatta quando modifichi Honcho e gli utenti vi accedono via rete. Mem0, Letta e cognee sono Apache-2.0 e LangMem è MIT, quindi Honcho è l'eccezione copyleft tra i livelli di memoria dedicati. Non è consulenza legale.\n\nPrima di impegnarti, esegui il quickstart con i $5 di credito su un vero log di conversazione.\n\n## Domande frequenti\n\n### Honcho memory è gratuito?\n\nIn parte. Il cloud offre $5 di credito, più $5 al mese con una carta, e le startup che hanno raccolto meno di $5M possono ottenere $1,000 di credito. Il self-hosted non ha costi di licenza con l'AGPL-3.0, ma paghi tu le fatture di LLM ed embedding.\n\n### Posso usare Honcho in un SaaS closed source?\n\nSì, se la tua app chiama un server Honcho non modificato tramite la sua API. Se modifichi Honcho e lo esponi via rete, la sezione 13 dell'AGPL richiede di offrire il sorgente di quella versione modificata. La tua app resta chiusa. Non è consulenza legale; chiedi a un legale se fai un fork.\n\n### Honcho vs Mem0 o Hindsight: quale scegliere?\n\nScegli Mem0 (Apache-2.0) per partire più in fretta, Hindsight (MIT) per risparmiare token e Honcho per la modellazione dell'utente. Uno sviluppatore segnala che Hindsight «used far fewer tokens» su Hermes ([X, ott 2026](https://x.com/StillYazeed/status/2115014740145512772)). Il blog di Mem0 dice che Honcho non ha benchmark pubblici, eppure dal 2025-12-19 ne ha pubblicati 21 file di risultati grezzi. Vedi [la classifica completa](/it/blog/migliori-strumenti-memoria-agenti-ia).\n\n```references\ntitle: Fonti\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min di lettura","featured":false,"tags":["honcho memory","honcho ai","plastic labs","memoria agenti ia","honcho memory recensione"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Punteggio di Honcho memory su LongMemEval S pari al 90,4%, riprodotto nel nostro ricalcolo, su un grafo di memoria","seo":{"metaTitle":"Honcho memory: recensione, pro, contro e benchmark ricontato","metaDescription":"Honcho memory vale la pena? Il nostro nuovo conteggio ha riprodotto il suo 90,4% di benchmark. Pro, contro, prezzi reali e chi lo usa e perché, nel 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:07.758Z","createdAt":"2026-10-28T16:06:32.042Z","_status":"published"},{"id":8822,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho memory : test et avis, 90,4 % confirmé par notre recalcul (avantages et limites)","slug":"honcho-memory-test-avis","language":"fr","excerpt":"Nous avons recompté les fichiers de résultats bruts de Honcho : le score de 90,4 % sur LongMemEval S se reproduit à l'identique, et l'avance sur LoCoMo face à Haiku seul tombe à 6,3 points à questions égales. Avantages, limites, tarifs réels et qui l'utilise.","body":"# Honcho memory : test et avis, 90,4 % confirmé par notre recalcul (avantages et limites)\n\n**Honcho memory**, la [couche de mémoire pour agents IA](/fr/blog/guide-memoire-agents-ia) de Plastic Labs sous licence AGPL-3.0, annonce 90,4 % sur LongMemEval S. Notre test du 28 octobre 2026 a recompté ses fichiers de résultats bruts et trouvé le même score : 452 réponses justes sur 500. Sur LoCoMo, avec les mêmes 1 540 questions des deux côtés, l'avance de Honcho sur Claude Haiku 4.5 seul est de **6,3 points**, et non les 14,3 publiés.\n\nUne bonne mémoire. Une avance plus modeste. De vrais compromis.\n\n## Honcho memory vaut-il le coup ? Le verdict en un tableau\n\nChoisis Honcho si ton agent doit modéliser une personne pendant des mois ; passe ton chemin pour du RAG documentaire, un rappel instantané ou un fork propriétaire.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) est la seule option **AGPL-3.0** parmi les couches de mémoire dédiées (Mem0, Letta et cognee sont sous Apache-2.0, LangMem sous MIT), et son cloud facture le raisonnement à chaque requête en plus de l'ingestion.\n\n| Question | Réponse |\n|---|---|\n| Prix du service managé (vérifié le 2026-10-28) | $2 par 1M de tokens ingérés ; de $0.001 à $0.50 par requête de raisonnement ; `context()` illimité ; $5 de crédit offert |\n| Prérequis pour l'auto-hébergement | Postgres avec pgvector, un worker deriver, une clé LLM avec tool calling |\n| Benchmarks | LongMemEval S 90,4 %, LoCoMo 89,9 % (auto-déclarés ; avance à questions égales : +27,8 et +6,3) |\n| Idéal pour | Les agents qui modélisent une personne dans la durée |\n| À éviter pour | RAG documentaire, rappel au tour suivant, forks propriétaires ([notre classement des outils de mémoire](/fr/blog/meilleurs-outils-memoire-agents-ia) place Honcho en #3) |\n\nLes anciens tests citent encore $100 de crédits offerts. La documentation annonce désormais $5, plus $5 par mois avec une carte.\n\n## Comment fonctionne Honcho memory ?\n\nTon application écrit des messages entre des peers, puis un worker en arrière-plan les transforme en conclusions que tu interroges en langage naturel ou récupères comme contexte.\n\nUn peer est n'importe quel participant, utilisateur ou agent. Le quickstart v3 de la [documentation Honcho](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) montre tout le flux (code source sur [GitHub](https://github.com/plastic-labs/honcho)) :\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` répond aux questions posées en langage naturel. La [recherche hybride BM25 + vectorielle](/fr/blog/recherche-hybride-bm25-vs-vector) retrouve les messages et les conclusions, c'est-à-dire les faits dérivés par Honcho. `session.context(summary=True, tokens=10_000)` renvoie un [contexte limité en tokens](/fr/blog/guide-context-engineering) prêt à injecter dans un prompt.\n\nLe raisonnement est asynchrone. Un nouveau fait apparaît une fois le deriver passé, pas à la lecture suivante ; l'endpoint `representation` du README est la voie à faible latence.\n\n## Le score LoCoMo de 89,9 % de Honcho tient-il ? Nous avons recompté les fichiers bruts\n\nLes scores de 89,9 % et 90,4 % se reproduisent tous deux depuis les fichiers bruts de Plastic Labs ; sur LoCoMo, en revanche, l'avance à questions égales sur Haiku seul est de 6,3 points.\n\nLe 28 octobre 2026, nous avons recompté trois fichiers de résultats du dépôt [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (dossier de run `a1d689b`, nommé d'après le commit de Honcho testé). La colonne « publié » est auto-déclarée sur [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Publié | Notre recomptage | Avance à questions égales |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90,4 % (baseline 62,6 %) | 452/500 | +27,8 |\n| LoCoMo, Honcho | 89,9 % | 89,9 %, 1 540 questions | n/a |\n| LoCoMo, Haiku 4.5 seul | 75,6 % | 75,4 % avec 446 questions adversariales ; 83,6 % sur les mêmes 1 540 | +6,3, pas +14,3 |\n\nLe test montre où part l'écart. La baseline publiée inclut 446 questions adversariales, sur lesquelles Haiku obtient 46,2 %, alors que le run de Honcho n'en contenait aucune. L'article de Plastic Labs lui-même, [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho), écrit « Haiku alone scores 83.9% », proche de nos 83,6 %. La page d'évals compare simplement deux jeux de questions différents.\n\nSur les historiques courts, la raison de choisir Honcho est de consommer moins de tokens, pas d'être plus précis. Les historiques de [LoCoMo](https://arxiv.org/abs/2402.17753), de 16K à 26K tokens, tiennent dans n'importe quelle fenêtre de 200K, et [ConvoMem](https://arxiv.org/abs/2511.10523) a constaté que le contexte complet atteint 70 à 82 % en dessous d'environ 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S est différent : avec environ 115K tokens par historique, l'avance de +27,8 tient. Une précision de périmètre. Ces runs datent d'une configuration de décembre 2025 avec un dialectic Haiku 4.5. La config du dépôt open source utilise `gpt-5.4-mini` par défaut, mais ce n'est que la valeur du dépôt : en production, Plastic Labs fait tourner d'autres modèles, non publiés.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Pourquoi les développeurs choisissent-ils Honcho ?\n\nHoncho gagne sur la **modélisation de l'utilisateur**, parce qu'il tient à jour un portrait de qui est la personne, et cette mémoire la suit d'un outil d'agent à l'autre.\n\nVectorize (éditeur de Hindsight, un concurrent) a publié en mars 2026 une [comparaison des fournisseurs de mémoire pour Hermes](https://vectorize.io/articles/hermes-agent-memory-providers-compared) qui décrit Honcho comme un modèle comportemental de l'utilisateur, « not just a fact store ». Chaque raison a son revers.\n\n| Raison | Preuve | Revers |\n|---|---|---|\n| Il modélise la personne | « Great on knowing who YOU are » ([r/hermesagent, mai 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` est un appel LLM en direct, donc chaque question ajoute une vraie latence |\n| Une mémoire partagée entre les outils | Plugins pour Claude Code, Codex, Cursor, OpenCode, OpenClaw et Hermes, plus un [serveur MCP](/fr/blog/meilleurs-serveurs-mcp-claude-code) open source, hébergé sur `mcp.honcho.dev` ou auto-hébergé | Texte uniquement pour l'instant, avec un OCR très limité pour les documents |\n| Précision dans les tests d'utilisateurs | Un comparatif de six fournisseurs sur Qwen3.5 4B : Honcho « performed the best » ([r/hermesagent, août 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Avec les réglages par défaut du plugin, « almost 3 times the tokens of the next best performer » |\n| Confidentialité | Cité par ceux qui l'auto-hébergent ([Elkim, avr. 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (voir les limites) |\n\nC'est sur les économies de tokens que le marketing prend de l'avance. La page d'accueil promet 60 à 90 %, mais la [page d'évals](https://honcho.dev/evals) affiche 89 % sur LongMemEval S, 52 % sur LoCoMo et 16 % sur BEAM 100K. Un développeur cité sur la page d'accueil rapporte 10 à 15 %.\n\n## Qui utilise Honcho, et pour qui est-il fait ?\n\n542 206 téléchargements du SDK Python sur le mois jusqu'au 28 octobre 2026 montrent que Honcho a de vrais utilisateurs, surtout des développeurs d'agents autour de Hermes et des agents de code.\n\n```stats\ncaption: Signaux d'adoption, relevés le 2026-10-28.\nitems:\n  - value: 542206\n    label: téléchargements PyPI de honcho-ai, dernier mois\n    source: pypistats.org\n  - value: 101791\n    label: téléchargements npm de @honcho-ai/sdk, du 27 sept. au 26 oct.\n    source: api.npmjs.org\n  - value: 7803\n    label: étoiles GitHub, 954 forks\n    source: GitHub API\n```\n\nLa page d'accueil intitule sa bande de logos « Used by developers at » (utilisé par des développeurs chez). Cela désigne des développeurs individuels au sein de ces organisations, pas des contrats à l'échelle de l'entreprise ni des études de cas.\n\n| Groupe | Exemples tirés de honcho.dev |\n|---|---|\n| Grandes entreprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| Équipes IA | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Recherche | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\n[Hermes Agent](/fr/blog/hermes-agent-v0-15), de Nous Research, livre Honcho comme plugin de mémoire (`hermes plugins install honcho`), et la [documentation Hermes sur Honcho](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) recense cinq outils, de `honcho_profile` à `honcho_conclude`.\n\nPopularité ne vaut pas consensus. Un sondage de 138 réponses sur X autour de Hermes ([oct. 2026](https://x.com/HermesWatcher/status/2114492238659305561)) place les notes Markdown en tête (27), Hindsight deuxième (25) et Honcho troisième (22).\n\n- Bon choix : compagnons, tuteurs et agents de coaching\n- Bon choix : agents de code personnels partagés entre Claude Code, Codex et Cursor\n- Mauvais choix : RAG documentaire, rappel au tour suivant, forks propriétaires\n\n## Avantages et limites de Honcho : que paie-t-on pour la précision ?\n\nLa précision de Honcho est réelle ; le prix à payer, c'est la latence, la surconsommation de tokens, une pile d'auto-hébergement lourde et l'AGPL, donc prévois de les assumer tous les quatre.\n\nL'auto-hébergement demande Postgres avec [pgvector](/fr/blog/qdrant-vs-chroma-vs-pgvector-comparaison), un worker deriver et un LLM compatible tool calling (valeurs par défaut de la config du dépôt : `gpt-5.4-mini`, `text-embedding-3-small`). La CLI démarre l'API, le deriver, Postgres et Redis ; Docker Compose fonctionne aussi. Si les données de tes utilisateurs doivent rester en Europe, un hébergeur européen (Hetzner, OVH, Scaleway) convient : avec l'AGPL-3.0 en auto-hébergement, la mémoire persistée reste chez toi.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # traiter les petits lots tout de suite\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Avantages : là où Honcho mérite sa place\n\n- Une modélisation de l'utilisateur que les développeurs décrivent comme « savoir qui tu es »\n- Le meilleur résultat sur longs historiques de notre recomptage : +27,8 sur LongMemEval S\n- Open source, auto-hébergeable, avec des plugins pour Claude Code, Codex, Cursor, Hermes et d'autres\n\n### Limites : ce que ça te coûte\n\n- Latence. Des développeurs rapportent une trace dialectic `minimal` de 9,1 s ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) et 2,16 s ajoutées à chaque tour d'API Hermes ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). Le « ~200 ms » de la page d'accueil est une affirmation du fournisseur sur `context()`.\n- Coût des requêtes. Pour 10 000 utilisateurs qui ajoutent 20K tokens par mois, l'ingestion coûte **$400**, mais 30 requêtes de niveau Low chacun coûtent **$3,000** (Minimal : $300). C'est le niveau de requête, pas l'ingestion, qui décide de ta facture Honcho.\n- Entretien de l'auto-hébergement et dépendance. Tu fais tourner toi-même l'API, le deriver, Postgres, Redis et un LLM. Passer du cloud à l'auto-hébergement (ou l'inverse) implique de rejouer les messages, car les embeddings ne sont pas exportés ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. Un article comparatif affirme que l'auto-hébergement t'oblige à publier le code source de ton application. C'est exagéré : l'[article 13 de l'AGPL](https://www.gnu.org/licenses/agpl-3.0.html) s'applique quand tu modifies Honcho et que des utilisateurs y accèdent via un réseau. Mem0, Letta et cognee sont sous Apache-2.0 et LangMem sous MIT, donc Honcho est le seul sous copyleft parmi les couches de mémoire dédiées. Ceci n'est pas un avis juridique.\n\nLance le quickstart avec le crédit de $5 sur un vrai journal de conversation avant de t'engager.\n\n## Questions fréquentes\n\n### Honcho memory est-il gratuit ?\n\nEn partie. Le cloud offre $5 de crédit, plus $5 par mois avec une carte, et les startups ayant levé moins de $5M peuvent obtenir $1,000 de crédits. L'auto-hébergement n'entraîne aucun frais de licence sous AGPL-3.0, mais tu paies tes propres factures de LLM et d'embeddings.\n\n### Puis-je utiliser Honcho dans un SaaS propriétaire ?\n\nOui, si ton application appelle un serveur Honcho non modifié via son API. Si tu modifies Honcho et que tu le sers sur un réseau, l'article 13 de l'AGPL exige de proposer le code source de ce Honcho modifié. Ton application reste fermée. Ceci n'est pas un avis juridique ; demande conseil à un juriste si tu forkes.\n\n### Honcho vs Mem0 ou Hindsight : lequel choisir ?\n\nPrends Mem0 (Apache-2.0) pour démarrer le plus vite, Hindsight (MIT) pour économiser des tokens, et Honcho pour la modélisation de l'utilisateur. Un développeur rapporte que Hindsight a « used far fewer tokens » sur Hermes ([X, oct. 2026](https://x.com/StillYazeed/status/2115014740145512772)). Le blog de Mem0 affirme que Honcho n'a pas de benchmarks publics, alors qu'il a publié 21 fichiers de résultats bruts depuis le 2025-12-19. Voir [le classement complet](/fr/blog/meilleurs-outils-memoire-agents-ia).\n\n```references\ntitle: Références\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min de lecture","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Score de 90,4 % de Honcho memory sur LongMemEval S, reproduit dans notre recalcul, sur un graphe de mémoire","seo":{"metaTitle":"Honcho memory : test, avis, avantages et limites","metaDescription":"Honcho memory vaut-il le coup ? Notre test reproduit son score de 90,4 %. Avantages, limites, tarifs réels, auto-hébergement et qui l'utilise en 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:07.375Z","createdAt":"2026-10-28T16:06:31.770Z","_status":"published"},{"id":8821,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory: el 90,4 % aguanta nuestro recálculo, con pros y contras","slug":"honcho-memory-review","language":"es","excerpt":"Recontamos los archivos de resultados de Honcho: el 90,4 % en LongMemEval S se reproduce exacto, y en LoCoMo la ventaja sobre Haiku solo es de 6,3 puntos con el mismo conjunto de preguntas. Pros, contras, precios reales y quién lo usa.","body":"# Honcho Memory: el 90,4 % aguanta nuestro recálculo, con pros y contras\n\n**Honcho Memory**, la [capa de memoria para agentes de IA](/es/blog/guia-memoria-agentes-ia) de Plastic Labs con licencia AGPL-3.0, declara un 90,4 % en LongMemEval S. En nuestras pruebas del 28 de octubre de 2026 recontamos sus archivos de resultados sin procesar y obtuvimos los mismos 452 de 500. En LoCoMo, con ambos sistemas respondiendo las mismas 1.540 preguntas, la ventaja de Honcho sobre Claude Haiku 4.5 a secas es de **6,3 puntos**, no los 14,3 publicados.\n\nBuena memoria. Ventaja menor. Compromisos reales.\n\n## ¿Vale la pena Honcho Memory? El veredicto en una tabla\n\nUsa Honcho si tu agente debe modelar a una persona durante meses; descártalo para RAG sobre documentos, recuerdo instantáneo o un fork de código cerrado.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) es la única opción **AGPL-3.0** entre las capas de memoria dedicadas (Mem0, Letta y cognee son Apache-2.0, LangMem es MIT), y su cloud factura el razonamiento por consulta además de la ingesta.\n\n| Pregunta | Respuesta |\n|---|---|\n| Precio gestionado (comprobado el 2026-10-28) | $2 por 1M de tokens ingeridos; de $0.001 a $0.50 por consulta de razonamiento; `context()` ilimitado; $5 de crédito gratis |\n| Autoalojarlo requiere | Postgres con pgvector, un worker deriver y una clave de LLM con llamadas a herramientas |\n| Benchmarks | LongMemEval S 90,4 %, LoCoMo 89,9 % (autodeclarados; mejora en igualdad de condiciones +27,8 y +6,3) |\n| Ideal para | Agentes que modelan a una persona a lo largo del tiempo |\n| Elige otra cosa para | RAG sobre documentos, recuerdo en el siguiente turno, forks de código cerrado ([nuestro ranking de herramientas de memoria](/es/blog/mejores-herramientas-memoria-agentes-ia) pone a Honcho en el puesto 3) |\n\nLas reseñas antiguas aún citan $100 de crédito gratis. La documentación actual dice $5, más $5 al mes si añades una tarjeta.\n\n## Qué es Honcho Memory y cómo funciona\n\nTu aplicación escribe mensajes entre peers, y un worker en segundo plano los convierte en conclusiones que puedes consultar en lenguaje natural o extraer como contexto.\n\nUn peer es cualquier participante, usuario o agente. El quickstart de la v3 en la [documentación de Honcho](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) muestra todo el flujo (código en [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` responde preguntas en lenguaje natural. La [búsqueda híbrida BM25 + vectores](/es/blog/busqueda-hibrida-bm25-vs-vector) encuentra mensajes y conclusiones, que son los hechos derivados de Honcho. `session.context(summary=True, tokens=10_000)` devuelve [contexto con presupuesto de tokens](/es/blog/guia-context-engineering) listo para el prompt.\n\nEl razonamiento es asíncrono. Un hecho nuevo aparece cuando el deriver termina de ejecutarse, no en la siguiente lectura; el endpoint `representation` del README es la vía de baja latencia.\n\n## ¿Resiste el 89,9 % de Honcho en LoCoMo? Recalculamos los archivos originales\n\nTanto el 89,9 % como el 90,4 % se reproducen con los archivos originales de Plastic Labs; en LoCoMo, sin embargo, la ventaja en igualdad de condiciones sobre Haiku a secas es de 6,3 puntos.\n\nEl 28 de octubre de 2026 recontamos tres archivos de resultados de [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (carpeta de ejecución `a1d689b`, que lleva el nombre del commit de Honcho evaluado). La columna publicada es autodeclarada en [honcho.dev/evals](https://honcho.dev/evals).\n\n| Ejecución | Publicado | Nuestro recuento | Mejora en igualdad de condiciones |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90,4 % (línea base 62,6 %) | 452/500 | +27,8 |\n| LoCoMo, Honcho | 89,9 % | 89,9 %, 1.540 preguntas | n/d |\n| LoCoMo, solo Haiku 4.5 | 75,6 % | 75,4 % con 446 adversariales; 83,6 % en las mismas 1.540 | +6,3, no +14,3 |\n\nLa prueba muestra a dónde se va la diferencia. La línea base publicada incluye 446 preguntas adversariales, en las que Haiku sacó un 46,2 %, y la ejecución de Honcho no tenía ninguna. El propio post de Plastic Labs, [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho), dice que «Haiku alone scores 83.9%», muy cerca de nuestro 83,6 %. La página de evals simplemente compara dos conjuntos de preguntas distintos.\n\nEn historiales cortos, la razón para elegir Honcho es gastar menos tokens, no ganar precisión. Los historiales de [LoCoMo](https://arxiv.org/abs/2402.17753), de 16K a 26K tokens, caben en cualquier ventana de 200K, y [ConvoMem](https://arxiv.org/abs/2511.10523) halló que el contexto completo alcanza entre un 70 y un 82 % con menos de unas 150 conversaciones.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S es otra historia: con unos 115K tokens por historial, la ventaja de +27,8 se sostiene. Una aclaración de alcance. Estas ejecuciones usaron una configuración de diciembre de 2025 con un dialectic basado en Haiku 4.5. La configuración del repo open source usa `gpt-5.4-mini` por defecto, pero eso es solo el valor del repo; en producción Plastic Labs usa otros modelos que no publica.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## ¿Por qué los desarrolladores eligen Honcho?\n\nHoncho gana en **modelado de usuario**: mantiene una imagen continua de quién es alguien, y esa memoria lo acompaña entre sus herramientas de agentes.\n\nVectorize (creadora de Hindsight, su rival) publicó en marzo de 2026 una [comparativa de proveedores de memoria para Hermes](https://vectorize.io/articles/hermes-agent-memory-providers-compared) que lo describe como un modelo de comportamiento del usuario, «not just a fact store». Cada motivo tiene su pega.\n\n| Motivo | Evidencia | Pega |\n|---|---|---|\n| Modela a la persona | «Great on knowing who YOU are» ([r/hermesagent, mayo de 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` es una llamada en vivo a un LLM, así que cada pregunta añade latencia real |\n| Una memoria para todas las herramientas | Plugins para Claude Code, Codex, Cursor, OpenCode, OpenClaw y Hermes, más un [servidor MCP](/es/blog/mejores-servidores-mcp-claude-code) de código abierto, alojado en `mcp.honcho.dev` o autoalojado | Por ahora solo texto, con OCR muy limitado para documentos |\n| Precisión en pruebas de usuarios | Una comparativa de seis proveedores con Qwen3.5 4B: Honcho «performed the best» ([r/hermesagent, ago. de 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Con la configuración por defecto del plugin, «almost 3 times the tokens of the next best performer» |\n| Privacidad | Quienes lo autoalojan lo citan ([Elkim, abr. de 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (ver contras) |\n\nEl ahorro de tokens es donde el marketing se adelanta a los datos. La página principal anuncia un 60-90 %, pero la [página de evals](https://honcho.dev/evals) lista un 89 % en LongMemEval S, un 52 % en LoCoMo y un 16 % en BEAM 100K. Un desarrollador citado en la home reporta un 10-15 %.\n\n## ¿Quién usa Honcho y para quién es?\n\nLas 542.206 descargas del SDK de Python en el mes hasta el 28 de octubre de 2026 indican que Honcho tiene usuarios reales, sobre todo quienes construyen agentes alrededor de Hermes y de agentes de programación.\n\n```stats\ncaption: Señales de adopción, consultadas el 2026-10-28.\nitems:\n  - value: 542206\n    label: descargas de honcho-ai en PyPI, último mes\n    source: pypistats.org\n  - value: 101791\n    label: descargas de @honcho-ai/sdk en npm, del 27 de sep. al 26 de oct.\n    source: api.npmjs.org\n  - value: 7803\n    label: estrellas en GitHub, 954 forks\n    source: GitHub API\n```\n\nLa home etiqueta su tira de logos como «Used by developers at». Eso significa desarrolladores individuales de esas organizaciones, no contratos de toda la empresa ni casos de estudio.\n\n| Grupo | Ejemplos de honcho.dev |\n|---|---|\n| Grandes empresas | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| Equipos de IA | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Investigación | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\n[Hermes Agent](/es/blog/hermes-agent-v0-15), de Nous Research, incluye Honcho como plugin de memoria (`hermes plugins install honcho`), y la [documentación de Hermes sobre Honcho](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) lista cinco herramientas, desde `honcho_profile` hasta `honcho_conclude`.\n\nPopularidad no es consenso. Una encuesta de 138 respuestas sobre Hermes en X ([oct. de 2026](https://x.com/HermesWatcher/status/2114492238659305561)) puso primero las notas en Markdown (27), segundo a Hindsight (25) y tercero a Honcho (22).\n\n- Buen encaje: compañeros virtuales, tutores y agentes de coaching\n- Buen encaje: agentes de programación personales compartidos entre Claude Code, Codex y Cursor\n- Mal encaje: RAG sobre documentos, recuerdo en el siguiente turno, forks de código cerrado\n\n## Pros y contras de Honcho: ¿qué cedes a cambio de la precisión?\n\nLa precisión de Honcho es real; el precio son la latencia, la sobrecarga de tokens, un stack pesado para autoalojar y la AGPL, así que presupuesta los cuatro.\n\nAutoalojarlo requiere Postgres con [pgvector](/es/blog/qdrant-vs-chroma-vs-pgvector-comparacion), un worker deriver y un LLM con llamadas a herramientas (valores por defecto de la configuración del repo: `gpt-5.4-mini`, `text-embedding-3-small`). La CLI arranca la API, el deriver, Postgres y Redis; Docker Compose también funciona.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # procesar lotes pequeños al momento\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: dónde se gana su lugar\n\n- Modelado de usuario que los desarrolladores describen como «saber quién eres»\n- El mejor resultado en historiales largos de nuestro recuento: +27,8 en LongMemEval S\n- Open source, autoalojable, con plugins para Claude Code, Codex, Cursor, Hermes y más\n\n### Contras: lo que te cuesta\n\n- Latencia. Los desarrolladores reportan una traza de dialectic `minimal` de 9.1 s ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) y 2.16 s añadidos a cada turno de la API en Hermes ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). Los «~200 ms» de la home son una afirmación del proveedor sobre `context()`.\n- Coste por consulta. Con 10.000 usuarios que añaden 20K tokens al mes, la ingesta cuesta **$400**, pero 30 consultas de nivel Low por usuario cuestan **$3,000** (Minimal: $300). El nivel de consulta, no la ingesta, decide tu factura de Honcho.\n- Mantenimiento del autoalojado y dependencia. Tú ejecutas la API, el deriver, Postgres, Redis y un LLM. Pasar del cloud al autoalojado (o al revés) implica reenviar los mensajes, porque los embeddings no se exportan ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. Un artículo comparativo afirma que autoalojarlo te obliga a publicar el código de tu app. Exagera: la [sección 13 de la AGPL](https://www.gnu.org/licenses/agpl-3.0.html) se aplica cuando modificas Honcho y los usuarios acceden a él por red. Mem0, Letta y cognee son Apache-2.0 y LangMem es MIT, así que Honcho es la excepción copyleft entre las capas de memoria dedicadas. No es asesoramiento legal.\n\nAntes de comprometerte, ejecuta el quickstart con el crédito de $5 y un registro de conversación real.\n\n## Preguntas frecuentes\n\n### ¿Es gratis Honcho Memory?\n\nEn parte. El cloud da $5 de crédito, más $5 al mes con tarjeta, y las startups con menos de $5M recaudados pueden obtener $1,000 en créditos. Autoalojarlo no tiene coste de licencia bajo AGPL-3.0, pero pagas tus propias facturas de LLM y embeddings.\n\n### ¿Puedo usar Honcho en un SaaS de código cerrado?\n\nSí, si tu app llama a un servidor Honcho sin modificar a través de su API. Si modificas Honcho y lo sirves por red, la sección 13 de la AGPL exige ofrecer el código fuente de esa versión modificada. Tu propia app sigue siendo cerrada. No es asesoramiento legal; consulta a un abogado si haces un fork.\n\n### Honcho frente a Mem0 o Hindsight: ¿cuál elegir?\n\nElige Mem0 (Apache-2.0) para empezar más rápido, Hindsight (MIT) para ahorrar tokens y Honcho para modelado de usuario. Un desarrollador reporta que Hindsight «used far fewer tokens» en Hermes ([X, oct. de 2026](https://x.com/StillYazeed/status/2115014740145512772)). El blog de Mem0 dice que Honcho no tiene benchmarks públicos, pero ha publicado 21 archivos de resultados sin procesar desde el 2025-12-19. Consulta [el ranking completo](/es/blog/mejores-herramientas-memoria-agentes-ia).\n\n```references\ntitle: Referencias\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"6 min de lectura","featured":false,"tags":["honcho memory","honcho ai","plastic labs","memoria para agentes de ia","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Puntuación de Honcho Memory en LongMemEval S: 90,4 %, reproducida en nuestro recálculo, sobre un grafo de memoria","seo":{"metaTitle":"Honcho Memory: pros, contras y benchmark recalculado","metaDescription":"¿Vale la pena Honcho Memory? Nuestras pruebas reproducen su 90,4 % en el benchmark. Pros, contras, precios reales y quién lo usa y por qué, en 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:07.012Z","createdAt":"2026-10-28T16:06:31.519Z","_status":"published"},{"id":8820,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory im Test: 90,4 % halten unserer Nachrechnung stand, plus Vor- und Nachteile","slug":"honcho-memory-review","language":"de","excerpt":"Wir haben Honchos rohe Benchmark-Dateien neu ausgezählt: Der Wert von 90,4 % auf LongMemEval S lässt sich exakt reproduzieren, und der Vorsprung auf LoCoMo gegenüber Haiku allein beträgt bei gleicher Fragenbasis 6,3 Punkte. Hier stehen Vor- und Nachteile, die echten Preise und wer Honcho nutzt.","body":"# Honcho Memory im Test: 90,4 % halten unserer Nachrechnung stand, plus Vor- und Nachteile\n\n**Honcho memory**, die AGPL-3.0-lizenzierte [Memory-Schicht für KI-Agenten](/de/blog/ki-agenten-gedaechtnis-guide) von Plastic Labs, meldet 90,4 % auf LongMemEval S. In unserem Test am 28. Oktober 2026 haben wir die rohen Ergebnisdateien neu ausgezählt und kamen auf dieselben 452 von 500. Auf LoCoMo beträgt Honchos Vorsprung vor reinem Claude Haiku 4.5 bei identischen 1.540 Fragen **6,3 Punkte**, nicht die veröffentlichten 14,3.\n\nGutes Gedächtnis. Kleinerer Vorsprung. Echte Kompromisse.\n\n## Lohnt sich Honcho Memory? Das Urteil in einer Tabelle\n\nNimm Honcho, wenn dein Agent über Monate ein Modell einer Person aufbauen soll. Lass es bleiben bei Dokumenten-RAG, sofortigem Abruf oder einem Closed-Source-Fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) ist unter den dedizierten Memory-Schichten die einzige Option unter **AGPL-3.0** (Mem0, Letta und cognee stehen unter Apache-2.0, LangMem unter MIT), und die Cloud berechnet Reasoning pro Abfrage zusätzlich zur Ingestion.\n\n| Frage | Antwort |\n|---|---|\n| Preis in der Cloud (geprüft am 28.10.2026) | $2 pro 1 Mio. verarbeitete Token; $0.001 bis $0.50 pro Reasoning-Abfrage; `context()` unbegrenzt; $5 Startguthaben |\n| Self-Hosting braucht | Postgres mit pgvector, einen Deriver-Worker, einen LLM-Key mit Tool-Calling |\n| Benchmarks | LongMemEval S 90,4 %, LoCoMo 89,9 % (selbst berichtet; Vorsprung bei gleicher Fragenbasis +27,8 und +6,3) |\n| Am besten für | Agenten, die eine einzelne Person über die Zeit modellieren |\n| Besser etwas anderes bei | Dokumenten-RAG, Abruf im nächsten Turn, Closed-Source-Forks ([unser Ranking der Memory-Tools](/de/blog/beste-ki-agenten-speicher-tools) setzt Honcho auf Platz 3) |\n\nÄltere Reviews nennen noch $100 Startguthaben. In den Docs stehen inzwischen $5, plus $5 im Monat mit hinterlegter Karte.\n\n## Wie funktioniert Honcho Memory?\n\nDeine App schreibt Nachrichten zwischen Peers, und ein Hintergrund-Worker macht daraus Schlussfolgerungen, die du in natürlicher Sprache abfragen oder als Kontext abrufen kannst.\n\nEin Peer ist jeder Teilnehmer, Nutzer oder Agent. Der v3-Quickstart in den [Honcho-Docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) zeigt den ganzen Ablauf (Quellcode auf [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` beantwortet Fragen in natürlicher Sprache. Die [hybride Suche aus BM25 und Vektoren](/de/blog/hybride-suche-bm25-vs-vektor) findet Nachrichten und Conclusions, so heißen Honchos abgeleitete Fakten. `session.context(summary=True, tokens=10_000)` liefert [Kontext mit Token-Budget](/de/blog/context-engineering-leitfaden) für einen Prompt.\n\nDas Reasoning läuft asynchron. Ein neuer Fakt taucht erst auf, nachdem der Deriver gelaufen ist, nicht beim nächsten Lesezugriff. Der `representation`-Endpunkt aus dem README ist der Weg mit niedriger Latenz.\n\n## Hält Honchos LoCoMo-Wert von 89,9 % stand? Wir haben die Rohdateien neu bewertet\n\n89,9 % und 90,4 % lassen sich beide aus den Rohdateien von Plastic Labs reproduzieren. Auf LoCoMo liegt der Vorsprung vor Haiku allein bei gleicher Fragenbasis aber nur bei 6,3 Punkten.\n\nAm 28. Oktober 2026 haben wir drei Ergebnisdateien aus [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) neu ausgezählt (Run-Ordner `a1d689b`, benannt nach dem getesteten Honcho-Commit). Die Spalte „Veröffentlicht“ ist selbst berichtet und stammt von [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Veröffentlicht | Unsere Nachzählung | Vorsprung bei gleicher Fragenbasis |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90,4 % (Baseline 62,6 %) | 452/500 | +27,8 |\n| LoCoMo, Honcho | 89,9 % | 89,9 %, 1.540 Fragen | n. v. |\n| LoCoMo, Haiku 4.5 allein | 75,6 % | 75,4 % mit 446 Adversarial-Fragen; 83,6 % auf denselben 1.540 | +6,3, nicht +14,3 |\n\nDie Nachzählung zeigt, wo die Differenz herkommt. Die veröffentlichte Baseline enthält 446 Adversarial-Fragen, bei denen Haiku 46,2 % erreichte, und Honchos Run hatte keine einzige. Der eigene Beitrag von Plastic Labs, [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho), nennt „Haiku alone scores 83.9%“, nah an unseren 83,6 %. Die Evals-Seite vergleicht schlicht zwei verschiedene Fragenmengen.\n\nBei kurzen Verläufen spricht für Honcho der geringere Token-Verbrauch, nicht höhere Genauigkeit. [LoCoMo](https://arxiv.org/abs/2402.17753)-Verläufe mit 16K bis 26K Token passen in jedes 200K-Fenster, und [ConvoMem](https://arxiv.org/abs/2511.10523) fand, dass der volle Kontext bei unter etwa 150 Gesprächen 70–82 % erreicht.\n\nBei [LongMemEval](https://arxiv.org/abs/2410.10813) S sieht es anders aus: Bei rund 115K Token pro Verlauf hält der Vorsprung von +27,8. Eine Einschränkung zum Umfang: Diese Runs liefen mit einem Setup von Dezember 2025 und einer Haiku-4.5-Dialektik. Die Konfiguration im Open-Source-Repo nutzt standardmäßig `gpt-5.4-mini`, aber das ist nur der Repo-Default; Plastic Labs setzt im Produktivbetrieb andere, nicht veröffentlichte Modelle ein.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Warum entscheiden sich Entwickler für Honcho?\n\nHoncho punktet beim **User Modeling**. Es führt ein laufendes Bild davon, wer jemand ist, und dieses Gedächtnis folgt der Person durch ihre Agent-Tools.\n\nVectorize (Hersteller des Konkurrenten Hindsight) nennt Honcho in einem [Vergleich von Hermes-Memory-Providern](https://vectorize.io/articles/hermes-agent-memory-providers-compared) vom März 2026 ein Verhaltensmodell des Nutzers, „not just a fact store“. Jeder Grund hat einen Haken.\n\n| Grund | Beleg | Haken |\n|---|---|---|\n| Es modelliert die Person | „Great on knowing who YOU are“ ([r/hermesagent, Mai 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` ist ein Live-LLM-Aufruf, jede Frage kostet also spürbar Latenz |\n| Ein Gedächtnis über mehrere Tools | Plugins für Claude Code, Codex, Cursor, OpenCode, OpenClaw und Hermes, dazu ein quelloffener [MCP-Server](/de/blog/beste-mcp-server-fuer-claude-code), gehostet unter `mcp.honcho.dev` oder selbst betrieben | Bisher nur Text, OCR für Dokumente ist sehr begrenzt |\n| Genauigkeit in Nutzertests | Bake-off mit sechs Providern auf Qwen3.5 4B: Honcho „performed the best“ ([r/hermesagent, Aug. 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | Mit den Standardeinstellungen des Plugins „almost 3 times the tokens of the next best performer“ |\n| Datenschutz | Self-Hoster führen es an ([Elkim, Apr. 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (siehe Nachteile) |\n\nBei den Token-Einsparungen eilt das Marketing den Zahlen voraus. Die Startseite wirbt mit 60–90 %, die [Evals-Seite](https://honcho.dev/evals) nennt aber 89 % auf LongMemEval S, 52 % auf LoCoMo und 16 % auf BEAM 100K. Ein auf der Startseite zitierter Builder berichtet von 10–15 %.\n\n## Wer nutzt Honcho, und für wen ist es gedacht?\n\n542.206 Downloads des Python-SDK im Monat bis zum 28. Oktober 2026 zeigen: Honcho hat echte Nutzer, überwiegend Agent-Builder rund um Hermes und Coding-Agenten.\n\n```stats\ncaption: Adoptionssignale, abgerufen am 28.10.2026.\nitems:\n  - value: 542206\n    label: PyPI-Downloads von honcho-ai, letzter Monat\n    source: pypistats.org\n  - value: 101791\n    label: npm-Downloads von @honcho-ai/sdk, 27. Sep. bis 26. Okt.\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub-Sterne, 954 Forks\n    source: GitHub API\n```\n\nDie Startseite beschriftet ihren Logo-Streifen mit „Used by developers at“. Gemeint sind einzelne Entwickler bei diesen Organisationen, keine unternehmensweiten Verträge und keine Fallstudien.\n\n| Gruppe | Beispiele von honcho.dev |\n|---|---|\n| Konzerne | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| KI-Teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Forschung | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nDer [Hermes Agent](/de/blog/hermes-agent-v0-15) von Nous Research liefert Honcho als Memory-Plugin aus (`hermes plugins install honcho`), und die [Hermes-Honcho-Docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) führen fünf Tools auf, von `honcho_profile` bis `honcho_conclude`.\n\nBeliebtheit ist kein Konsens. In einer Hermes-Umfrage auf X mit 138 Antworten ([Okt. 2026](https://x.com/HermesWatcher/status/2114492238659305561)) lagen Markdown-Notizen vorn (27), Hindsight auf Platz zwei (25) und Honcho auf Platz drei (22).\n\n- Gute Wahl: Companions, Tutoren und Coaching-Agenten\n- Gute Wahl: persönliche Coding-Agenten, die sich Claude Code, Codex und Cursor teilen\n- Schlechte Wahl: Dokumenten-RAG, Abruf im nächsten Turn, Closed-Source-Forks\n\n## Honcho: Vor- und Nachteile – was zahlst du für die Genauigkeit?\n\nHonchos Genauigkeit ist real. Den Preis zahlst du in Verzögerung, Token-Overhead, einem schweren Self-Hosting-Stack und der AGPL, plane also für alle vier.\n\nSelf-Hosting braucht Postgres mit [pgvector](/de/blog/qdrant-vs-chroma-vs-pgvector-vergleich), einen Deriver-Worker und ein LLM mit Tool-Calling (Standardwerte der Repo-Konfiguration: `gpt-5.4-mini`, `text-embedding-3-small`). Die CLI startet API, Deriver, Postgres und Redis; Docker Compose funktioniert ebenfalls.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # kleine Batches sofort verarbeiten\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Vorteile: wo Honcho seinen Platz verdient\n\n- User Modeling, das Entwickler als „weiß, wer du bist“ beschreiben\n- Das stärkste Ergebnis bei langen Verläufen in unserer Nachzählung: +27,8 auf LongMemEval S\n- Open Source, selbst hostbar, mit Plugins für Claude Code, Codex, Cursor, Hermes und mehr\n\n### Nachteile: was es dich kostet\n\n- Verzögerung. Entwickler berichten von einer 9,1 s langen `minimal`-Dialektik-Trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) und von 2,16 s zusätzlich bei jedem Hermes-API-Turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). Die „~200 ms“ der Startseite sind eine Herstellerangabe zu `context()`.\n- Abfragekosten. Bei 10.000 Nutzern mit je 20K Token pro Monat kostet die Ingestion **$400**, aber 30 Abfragen der Stufe Low pro Nutzer kosten **$3,000** (Minimal: $300). Die Abfrage-Stufe bestimmt deine Honcho-Rechnung, nicht die Ingestion.\n- Self-Hosting-Pflege und Lock-in. API, Deriver, Postgres, Redis und ein LLM betreibst du selbst. Wer zwischen Cloud und Self-Hosting wechselt, muss Nachrichten neu einspielen, weil Embeddings nicht exportiert werden ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. Ein Vergleichsartikel behauptet, Self-Hosting zwinge dich, den Quellcode deiner App offenzulegen. Das übertreibt: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) greift, wenn du Honcho modifizierst und Nutzer es über ein Netzwerk erreichen. Mem0, Letta und cognee stehen unter Apache-2.0, LangMem unter MIT. Honcho ist also der Copyleft-Ausreißer unter den dedizierten Memory-Schichten. Keine Rechtsberatung.\n\nSpiel den Quickstart mit dem $5-Guthaben und einem echten Gesprächsprotokoll durch, bevor du dich festlegst.\n\n## Häufige Fragen\n\n### Ist Honcho Memory kostenlos?\n\nTeilweise. Die Cloud gibt $5 Guthaben, plus $5 im Monat mit hinterlegter Karte, und Startups mit unter $5 Mio. Funding können $1,000 an Credits bekommen. Self-Hosting kostet unter AGPL-3.0 keine Lizenzgebühr, aber du zahlst deine LLM- und Embedding-Rechnungen selbst.\n\n### Kann ich Honcho in einem Closed-Source-SaaS einsetzen?\n\nJa, wenn deine App einen unmodifizierten Honcho-Server über seine API aufruft. Modifizierst du Honcho und stellst es über ein Netzwerk bereit, verlangt AGPL §13, dass du den Quellcode dieses modifizierten Honcho anbietest. Deine eigene App bleibt geschlossen. Keine Rechtsberatung; frag einen Anwalt, wenn du forkst.\n\n### Honcho vs. Mem0 oder Hindsight: Was soll ich nehmen?\n\nNimm Mem0 (Apache-2.0) für den schnellsten Start, Hindsight (MIT) zum Token-Sparen und Honcho für User Modeling. Ein Entwickler berichtet, Hindsight habe auf Hermes „used far fewer tokens“ ([X, Okt. 2026](https://x.com/StillYazeed/status/2115014740145512772)). Der Mem0-Blog behauptet, Honcho habe keine öffentlichen Benchmarks, dabei hat es seit dem 19.12.2025 21 rohe Ergebnisdateien veröffentlicht. Das [vollständige Ranking](/de/blog/beste-ki-agenten-speicher-tools) findest du hier.\n\n```references\ntitle: Quellen\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 Min. Lesezeit","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho Memory: LongMemEval-S-Wert von 90,4 %, in unserer Nachrechnung reproduziert, vor einem Graphen aus Speicherknoten","seo":{"metaTitle":"Honcho Memory im Test: Vor- und Nachteile, Benchmark geprüft","metaDescription":"Lohnt sich Honcho Memory? Unser Test reproduziert den Benchmark-Wert von 90,4 %. Dazu Vor- und Nachteile, echte Preise und wer es nutzt, Stand 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.344Z","createdAt":"2026-10-28T16:06:31.158Z","_status":"published"},{"id":8819,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho memory: نتيجة 90.4% تصمد في إعادة التصحيح لدينا، مع المزايا والعيوب","slug":"honcho-memory-review","language":"ar","excerpt":"أعدنا عدّ ملفات النتائج الخام لـ Honcho: نتيجة 90.4% على LongMemEval S تتكرر تمامًا، وتقدّمه على Haiku وحده في LoCoMo هو 6.3 نقطة في مقارنة متكافئة. إليك المزايا والعيوب والأسعار الفعلية ومن يستخدمه فعلًا.","body":"# Honcho memory: نتيجة 90.4% تصمد في إعادة التصحيح لدينا، مع المزايا والعيوب\n\n**Honcho memory** هو طبقة ذاكرة لوكلاء الذكاء الاصطناعي من Plastic Labs بترخيص AGPL-3.0، وهو [طبقة ذاكرة للوكلاء](/ar/mudawwana/dalil-dhakira-wukala-aldhaka-alaistinaeii) يدّعي 90.4% على LongMemEval S. اختبارنا في 28 أكتوبر 2026 أعاد عدّ ملفات نتائجه الخام وخرج بالرقم نفسه: 452 من 500. وفي LoCoMo، حين يجيب الطرفان عن الأسئلة نفسها (1,540 سؤالًا)، يتقدّم Honcho على Claude Haiku 4.5 العادي بـ **6.3 نقطة**، لا 14.3 كما في المنشور.\n\nذاكرة جيدة. تقدّم أصغر. مقايضات حقيقية.\n\n## هل يستحق Honcho memory الاستخدام؟ الحكم في جدول واحد\n\nاستخدم Honcho حين يجب أن يبني وكيلك نموذجًا لشخص على مدى أشهر؛ وتجاوزه إذا كنت تحتاج RAG للمستندات أو استدعاءً فوريًا أو نسخة مغلقة المصدر.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) هو الخيار الوحيد بترخيص **AGPL-3.0** بين طبقات الذاكرة المخصصة (Mem0 وLetta وcognee بترخيص Apache-2.0، وLangMem بترخيص MIT)، وسحابته تحاسب على الاستدلال لكل استعلام فوق تكلفة الإدخال.\n\n| السؤال | الجواب |\n|---|---|\n| السعر المُدار (تحققنا في 2026-10-28) | $2 لكل مليون رمز مُدخل؛ من $0.001 إلى $0.50 لكل استعلام استدلال؛ `context()` بلا حد؛ رصيد مجاني $5 |\n| متطلبات الاستضافة الذاتية | Postgres مع pgvector، وعامل deriver، ومفتاح LLM يدعم استدعاء الأدوات |\n| الاختبارات المعيارية | LongMemEval S 90.4%، LoCoMo 89.9% (أرقام ذاتية؛ التقدّم في مقارنة متكافئة +27.8 و+6.3) |\n| الأنسب لـ | وكلاء يبنون نموذجًا لشخص واحد عبر الزمن |\n| اختر غيره إن كنت تريد | RAG للمستندات، أو استدعاء الدور التالي، أو نسخًا مغلقة المصدر ([ترتيبنا لأدوات الذاكرة](/ar/mudawwana/%D8%A7%D9%81%D8%B6%D9%84-%D8%A7%D8%AF%D9%88%D8%A7%D8%AA-%D8%B0%D8%A7%D9%83%D8%B1%D8%A9-%D9%88%D9%83%D9%84%D8%A7%D8%A1-%D8%A7%D9%84%D8%B0%D9%83%D8%A7%D8%A1-%D8%A7%D9%84%D8%A7%D8%B5%D8%B7%D9%86%D8%A7%D8%B9%D9%8A-%D9%85%D8%B1%D8%AA%D8%A8%D8%A9) يضع Honcho في المرتبة 3) |\n\nما زالت مراجعات أقدم تذكر $100 رصيدًا مجانيًا. الوثائق تقول الآن $5، مع $5 شهريًا عند ربط بطاقة.\n\n## كيف يعمل Honcho memory؟\n\nيكتب تطبيقك الرسائل بين الأطراف (peers)، ويحوّلها عامل في الخلفية إلى استنتاجات تستعلم عنها بلغة طبيعية أو تسحبها كسياق.\n\nالطرف (peer) هو أي مشارك، مستخدمًا كان أم وكيلًا. تعرض البداية السريعة للإصدار v3 في [وثائق Honcho](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) التدفق كاملًا (الشيفرة المصدرية على [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\nيجيب `peer.chat()` عن الأسئلة بلغة طبيعية. و[البحث الهجين BM25 + المتجهات](/ar/mudawwana/al-bahth-al-hajin-bm25-vs-vector) يجد الرسائل والاستنتاجات، وهي الحقائق التي يشتقها Honcho. أما `session.context(summary=True, tokens=10_000)` فيعيد [سياقًا بميزانية رموز محددة](/ar/mudawwana/dalil-handasa-alsiyaq) للموجِّه (Prompt).\n\nالاستدلال غير متزامن. تظهر الحقيقة الجديدة بعد تشغيل deriver، لا عند القراءة التالية؛ ونقطة النهاية `representation` في README هي المسار منخفض زمن الاستجابة.\n\n## هل تصمد نتيجة Honcho البالغة 89.9% في LoCoMo؟ أعدنا تصحيح الملفات الخام\n\nالنتيجتان 89.9% و90.4% تتكرران من ملفات Plastic Labs الخام؛ لكن في LoCoMo يبلغ التقدّم المتكافئ على Haiku وحده 6.3 نقطة.\n\nفي 28 أكتوبر 2026 أعدنا عدّ ثلاثة ملفات نتائج من [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (مجلد التشغيل `a1d689b`، سُمّي باسم commit الذي اختُبر من Honcho). العمود المنشور ذاتي الإبلاغ على [honcho.dev/evals](https://honcho.dev/evals).\n\n| التشغيل | المنشور | إعادة عدّنا | التقدّم المتكافئ |\n|---|---|---|---|\n| LongMemEval S، Honcho | 90.4% (خط الأساس 62.6%) | 452/500 | +27.8 |\n| LoCoMo، Honcho | 89.9% | 89.9%، 1,540 سؤالًا | غير متاح |\n| LoCoMo، Haiku 4.5 وحده | 75.6% | 75.4% مع 446 سؤالًا عدائيًا؛ 83.6% على الأسئلة نفسها (1,540) | +6.3 لا +14.3 |\n\nاختبارنا يُظهر أين يذهب الفرق. خط الأساس المنشور يشمل 446 سؤالًا عدائيًا (adversarial) سجّل فيها Haiku نسبة 46.2%، ولم يكن في تشغيل Honcho أي منها. منشور Plastic Labs نفسه [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) يقول إن «Haiku وحده يسجّل 83.9%»، وهو قريب من 83.6% لدينا. صفحة evals تقارن ببساطة مجموعتين مختلفتين من الأسئلة.\n\nعلى التواريخ القصيرة، سبب اختيار Honcho هو رموز أقل لا دقة أعلى. تواريخ [LoCoMo](https://arxiv.org/abs/2402.17753) من 16 ألفًا إلى 26 ألف رمز تتسع في أي نافذة بحجم 200 ألف، ووجدت [ConvoMem](https://arxiv.org/abs/2511.10523) أن السياق الكامل يبلغ 70-82% تحت نحو 150 محادثة.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S مختلف: عند نحو 115 ألف رمز لكل تاريخ، يصمد التقدّم +27.8. ملاحظة نطاق واحدة: استخدمت هذه التشغيلات إعدادًا من ديسمبر 2025 مع dialectic على Haiku 4.5. تعتمد إعدادات المستودع مفتوح المصدر افتراضيًا `gpt-5.4-mini`، لكن هذا مجرد الافتراضي في المستودع؛ إذ تشغّل Plastic Labs في الإنتاج نماذج أخرى لا تنشرها.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## لماذا يختار المطورون Honcho؟\n\nيتفوق Honcho في **نمذجة المستخدم**: يحتفظ بصورة متجددة عمّن يكون الشخص، وتلحق به ذاكرته عبر أدوات وكلائه.\n\nكتبت Vectorize (صانعة Hindsight المنافس) في مارس 2026 [مقارنة لمزودي ذاكرة Hermes](https://vectorize.io/articles/hermes-agent-memory-providers-compared) وصفته فيها بأنه نموذج سلوكي للمستخدم، «لا مجرد مخزن حقائق». ولكل سبب ثغرة.\n\n| السبب | الدليل | الثغرة |\n|---|---|---|\n| ينمذج الشخص | «رائع في معرفة من أنت» ([r/hermesagent، مايو 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` استدعاء مباشر لنموذج LLM، لذا يضيف كل سؤال تأخيرًا ملموسًا |\n| ذاكرة واحدة عبر الأدوات | إضافات لـ Claude Code وCodex وCursor وOpenCode وOpenClaw وHermes، مع [خادم MCP](/ar/mudawwana/afdal-khawadim-mcp-claude-code) مفتوح المصدر، مستضاف على `mcp.honcho.dev` أو باستضافة ذاتية | نص فقط حاليًا، مع دعم محدود جدًا للتعرّف الضوئي (OCR) على المستندات |\n| الدقة في اختبارات المستخدمين | مقارنة بين ستة مزودين على Qwen3.5 4B: Honcho «أدّى الأفضل» ([r/hermesagent، أغسطس 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | مع الإعدادات الافتراضية للإضافة: «ما يقارب ثلاثة أضعاف رموز صاحب المركز التالي» |\n| الخصوصية | يذكرها من يستضيفونه ذاتيًا ([Elkim، أبريل 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (انظر العيوب) |\n\nتوفير الرموز هو الموضع الذي يسبق فيه التسويق الواقع. تعلن الصفحة الرئيسية 60-90%، لكن [صفحة evals](https://honcho.dev/evals) تسرد 89% على LongMemEval S و52% على LoCoMo و16% على BEAM 100K. ويذكر باني اقتُبس منه في الصفحة الرئيسية 10-15%.\n\n## من يستخدم Honcho ولمن هو؟\n\n542,206 تنزيلًا لحزمة Python في الشهر المنتهي في 28 أكتوبر 2026 تعني أن لـ Honcho مستخدمين حقيقيين، أغلبهم بناة وكلاء حول Hermes ووكلاء البرمجة.\n\n```stats\ncaption: مؤشرات الاعتماد، جُمعت في 2026-10-28.\nitems:\n  - value: 542206\n    label: تنزيلات honcho-ai على PyPI خلال الشهر الأخير\n    source: pypistats.org\n  - value: 101791\n    label: تنزيلات @honcho-ai/sdk على npm من 27 سبتمبر إلى 26 أكتوبر\n    source: api.npmjs.org\n  - value: 7803\n    label: نجمة على GitHub، و954 fork\n    source: GitHub API\n```\n\nتسمّي الصفحة الرئيسية شريط الشعارات «يستخدمه مطوّرون في». وهذا يعني مطوّرين أفرادًا يعملون في هذه المؤسسات، لا عقودًا على مستوى الشركات ولا دراسات حالة.\n\n| المجموعة | أمثلة من honcho.dev |\n|---|---|\n| الشركات الكبرى | Microsoft وNVIDIA وGitHub وCisco وAtlassian وCoinbase |\n| فرق الذكاء الاصطناعي | OpenRouter وNous Research وPolymarket وRaycast وChroma وHippocratic AI |\n| البحث | Stanford وUC Berkeley وCornell وJohns Hopkins APL وNYU |\n\nيشحن [Hermes Agent](/ar/mudawwana/hermes-agent-v0-15) من Nous Research مع Honcho كإضافة ذاكرة (`hermes plugins install honcho`)، وتسرد [وثائق Hermes عن Honcho](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) خمس أدوات، من `honcho_profile` إلى `honcho_conclude`.\n\nالشعبية ليست إجماعًا. في استطلاع من 138 إجابة حول Hermes على X ([أكتوبر 2026](https://x.com/HermesWatcher/status/2114492238659305561)) جاءت ملاحظات Markdown أولًا (27)، وHindsight ثانيًا (25)، وHoncho ثالثًا (22).\n\n- مناسب: الرفقاء الافتراضيون والمدرّسون ووكلاء التدريب\n- مناسب: وكلاء البرمجة الشخصيون المشتركون بين Claude Code وCodex وCursor\n- غير مناسب: RAG للمستندات، واستدعاء الدور التالي، والنسخ المغلقة المصدر\n\n## مزايا Honcho وعيوبه: ماذا تدفع مقابل الدقة؟\n\nدقة Honcho حقيقية؛ وثمنها التأخر وعبء الرموز وحزمة استضافة ذاتية ثقيلة وترخيص AGPL، فاحسب حسابها كلها.\n\nتحتاج الاستضافة الذاتية إلى Postgres مع [pgvector](/ar/mudawwana/qdrant-vs-chroma-vs-pgvector-muqarana) وعامل deriver ونموذج LLM يدعم استدعاء الأدوات (القيم الافتراضية في إعدادات المستودع: `gpt-5.4-mini` و`text-embedding-3-small`). يشغّل CLI الـ API وderiver وPostgres وRedis؛ ويعمل Docker Compose أيضًا.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### المزايا: أين يستحق Honcho مكانه\n\n- نمذجة مستخدم يصفها المطورون بأنها تعرف من أنت\n- أقوى نتيجة على التواريخ الطويلة في إعادة عدّنا: +27.8 على LongMemEval S\n- مفتوح المصدر وقابل للاستضافة الذاتية، مع إضافات لـ Claude Code وCodex وCursor وHermes وغيرها\n\n### العيوب: ما الذي يكلّفك\n\n- التأخر. يبلّغ مطورون عن أثر dialectic بمستوى `minimal` يستغرق 9.1 s ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) وعن 2.16 s تُضاف إلى كل دور في Hermes API ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). رقم «~200 ms» في الصفحة الرئيسية ادعاء من البائع عن `context()`.\n- تكلفة الاستعلام. لـ 10,000 مستخدم يضيف كلٌّ منهم 20 ألف رمز شهريًا، يبلغ الإدخال **$400**، لكن 30 استعلامًا من المستوى Low لكل منهم تبلغ **$3,000** (Minimal: $300). مستوى الاستعلام، لا الإدخال، هو ما يحدد فاتورة Honcho.\n- صيانة الاستضافة الذاتية والارتباط بالمنصة. تشغّل بنفسك الـ API وderiver وPostgres وRedis ونموذج LLM. والانتقال بين السحابة والاستضافة الذاتية يعني إعادة تشغيل الرسائل، لأن التضمينات لا تُصدَّر ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. يقول مقال مقارنة واحد إن الاستضافة الذاتية تُلزمك بنشر مصدر تطبيقك. هذا مبالغة: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) ينطبق حين تعدّل Honcho ويصل إليه المستخدمون عبر شبكة. Mem0 وLetta وcognee بترخيص Apache-2.0 وLangMem بترخيص MIT، فـ Honcho هو الشاذ ذو الـ copyleft بين طبقات الذاكرة المخصصة. ليست استشارة قانونية.\n\nشغّل البداية السريعة على رصيد $5 مع سجل محادثة حقيقي واحد قبل أن تلتزم.\n\n## الأسئلة الشائعة\n\n### هل Honcho memory مجاني؟\n\nجزئيًا. تمنحك السحابة رصيد $5، مع $5 شهريًا عند ربط بطاقة، ويمكن للشركات الناشئة التي جمعت أقل من $5M الحصول على رصيد $1,000. الاستضافة الذاتية بلا رسوم ترخيص بموجب AGPL-3.0، لكنك تدفع فواتير LLM والتضمين بنفسك.\n\n### هل أستخدم Honcho في SaaS مغلق المصدر؟\n\nنعم، إذا كان تطبيقك يستدعي خادم Honcho غير المعدّل عبر الـ API. وإذا عدّلت Honcho وقدّمته عبر شبكة، يُلزمك AGPL §13 بعرض مصدر Honcho المعدّل. يبقى تطبيقك مغلقًا. ليست استشارة قانونية؛ اسأل محاميًا إن عمل fork.\n\n### Honcho أم Mem0 أم Hindsight: أيها أختار؟\n\nاختر Mem0 (Apache-2.0) لأسرع بداية، وHindsight (MIT) لتوفير الرموز، وHoncho لنمذجة المستخدم. يبلّغ مطوّر أن Hindsight «استخدم رموزًا أقل بكثير» على Hermes ([X، أكتوبر 2026](https://x.com/StillYazeed/status/2115014740145512772)). مدونة Mem0 تقول إن Honcho بلا اختبارات معيارية علنية، لكنه نشر 21 ملف نتائج خام منذ 2025-12-19. انظر [الترتيب الكامل](/ar/mudawwana/%D8%A7%D9%81%D8%B6%D9%84-%D8%A7%D8%AF%D9%88%D8%A7%D8%AA-%D8%B0%D8%A7%D9%83%D8%B1%D8%A9-%D9%88%D9%83%D9%84%D8%A7%D8%A1-%D8%A7%D9%84%D8%B0%D9%83%D8%A7%D8%A1-%D8%A7%D9%84%D8%A7%D8%B5%D8%B7%D9%86%D8%A7%D8%B9%D9%8A-%D9%85%D8%B1%D8%AA%D8%A8%D8%A9).\n\n```references\ntitle: المراجع\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 دقائق قراءة","featured":false,"tags":["honcho memory","honcho ai","plastic labs","ذاكرة وكلاء الذكاء الاصطناعي","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"نتيجة Honcho memory على LongMemEval S بنسبة 90.4%، أعدنا إنتاجها في إعادة التصحيح، فوق رسم باهت لعقد الذاكرة","seo":{"metaTitle":"Honcho memory: المزايا والعيوب ونتيجة معاد تصحيحها","metaDescription":"هل يستحق Honcho memory الاستخدام؟ اختبارنا أعاد إنتاج نتيجته 90.4%. المزايا والعيوب والأسعار الفعلية ومن يستخدمه ولماذا، في 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":1,"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":1,"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":1,"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"},"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:05.931Z","createdAt":"2026-10-28T16:06:30.860Z","_status":"published"},{"id":8818,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons","slug":"honcho-memory-review","language":"en","excerpt":"We recounted Honcho's raw benchmark files: the 90.4% LongMemEval S score reproduces exactly, and the LoCoMo lead over Haiku alone is 6.3 points on a like-for-like count. Here are the pros, the cons, the real pricing and who actually uses it.","body":"# Honcho Memory Review: 90.4% Holds Up in Our Re-Score, Plus Pros and Cons\n\n**Honcho memory**, Plastic Labs' AGPL-3.0 [memory layer for AI agents](/en/blog/ai-agent-memory-guide), claims 90.4% on LongMemEval S. Our testing on 28 October 2026 recounted its raw result files and got the same 452 of 500. On LoCoMo, with both sides answering the same 1,540 questions, Honcho's lead over plain Claude Haiku 4.5 is **6.3 points**, not the published 14.3.\n\nGood memory. Smaller lead. Real trade-offs.\n\n## Is Honcho Memory Worth Using? The Verdict in One Table\n\nUse Honcho when your agent must model a person over months; skip it for document RAG, instant recall, or a closed-source fork.\n\n[Honcho](https://honcho.dev/?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) is the only **AGPL-3.0** option among the dedicated memory layers (Mem0, Letta and cognee are Apache-2.0, LangMem is MIT), and its cloud bills reasoning per query on top of ingestion.\n\n| Question | Answer |\n|---|---|\n| Managed price (checked 2026-10-28) | $2 per 1M ingested tokens; $0.001 to $0.50 per reasoning query; `context()` unlimited; $5 free credit |\n| Self-host needs | Postgres with pgvector, a deriver worker, an LLM key with tool calling |\n| Benchmarks | LongMemEval S 90.4%, LoCoMo 89.9% (self-reported; like-for-like lift +27.8 and +6.3) |\n| Best for | Agents that model one person over time |\n| Pick something else for | Document RAG, next-turn recall, closed-source forks ([our ranked memory tools](/en/blog/best-ai-agent-memory-tools) put Honcho #3) |\n\nOlder reviews still quote $100 in free credits. The docs now say $5, plus $5 a month with a card.\n\n## How Does Honcho Memory Work?\n\nYour app writes messages between peers, and a background worker turns them into conclusions you can query in plain language or pull as context.\n\nA peer is any participant, user or agent. The v3 quickstart in the [Honcho docs](https://honcho.dev/docs/v3/documentation/introduction/quickstart?utm_source=techsy&utm_medium=referral&utm_campaign=aeo-placements) shows the whole flow (source on [GitHub](https://github.com/plastic-labs/honcho)):\n\n```python\nimport os\nfrom honcho import Honcho\nhoncho = Honcho(workspace_id=\"my-app-testing\", api_key=os.environ[\"HONCHO_API_KEY\"])\nalice = honcho.peer(\"alice\")\ntutor = honcho.peer(\"tutor\")\nsession = honcho.session(\"session-1\")\nsession.add_messages([\n    alice.message(\"Hey there — can you help me with my math homework?\"),\n    tutor.message(\"Absolutely. Send me your first problem!\"),\n])\nanswer = alice.chat(\"What learning styles does the user respond to best?\")\n```\n\n`peer.chat()` answers plain-language questions. [Hybrid BM25 + vector search](/en/blog/hybrid-search-bm25-vs-vector) finds messages and conclusions, which are Honcho's derived facts. `session.context(summary=True, tokens=10_000)` returns [token-budgeted context](/en/blog/context-engineering-guide) for a prompt.\n\nReasoning is asynchronous. A new fact appears after the deriver runs, not on the next read; the README's `representation` endpoint is the low-latency path.\n\n## Does Honcho's 89.9% LoCoMo Score Hold Up? We Re-Scored the Raw Files\n\n89.9% and 90.4% both reproduce from Plastic Labs' raw files; on LoCoMo, though, the like-for-like lead over Haiku alone is 6.3 points.\n\nOn 28 October 2026 we recounted three result files from [honcho-benchmarks](https://github.com/plastic-labs/honcho-benchmarks) (run folder `a1d689b`, named after the Honcho commit tested). The published column is self-reported on [honcho.dev/evals](https://honcho.dev/evals).\n\n| Run | Published | Our recount | Like-for-like lift |\n|---|---|---|---|\n| LongMemEval S, Honcho | 90.4% (baseline 62.6%) | 452/500 | +27.8 |\n| LoCoMo, Honcho | 89.9% | 89.9%, 1,540 questions | n/a |\n| LoCoMo, Haiku 4.5 alone | 75.6% | 75.4% with 446 adversarial; 83.6% on the same 1,540 | +6.3, not +14.3 |\n\nTesting shows where the gap goes. The published baseline includes 446 adversarial questions, where Haiku scored 46.2%, and Honcho's run had none. Plastic Labs' own [Benchmarking Honcho](https://plasticlabs.ai/blog/research/Benchmarking-Honcho) post says \"Haiku alone scores 83.9%\", close to our 83.6%. The evals page simply compares two question sets.\n\nOn short histories, the reason to pick Honcho is fewer tokens, not higher accuracy. [LoCoMo](https://arxiv.org/abs/2402.17753) histories of 16K to 26K tokens fit any 200K window, and [ConvoMem](https://arxiv.org/abs/2511.10523) found full context reaches 70-82% under about 150 conversations.\n\n[LongMemEval](https://arxiv.org/abs/2410.10813) S is different: at about 115K tokens per history, the +27.8 lead holds. One scope note. These runs used a December 2025 setup with a Haiku 4.5 dialectic. The open-source repo's config defaults to `gpt-5.4-mini`, but that's only the repo default; Plastic Labs runs a different, unpublished model set in production.\n\n```python\n# files: github.com/plastic-labs/honcho-benchmarks, folder a1d689b\nimport json, statistics\ndef score(f, drop_adv=True):\n    per_conv = []\n    for c in json.load(open(f))[\"detailed_results\"]:\n        qs = [q for q in c[\"question_results\"] if not (drop_adv and q[\"category_name\"] == \"adversarial\")]\n        per_conv.append(sum(q[\"passed\"] for q in qs) / len(qs))\n    return round(100 * statistics.mean(per_conv), 1)\nprint(score(\"locomo_results_20251215_175728.json\"))                  # 89.9\nprint(score(\"locomo_baseline_results_20251215_184837.json\"))         # 83.6, same 1,540 Qs\nprint(score(\"locomo_baseline_results_20251215_184837.json\", False))  # 75.4, incl. adversarial\n```\n\n## Why Do Developers Choose Honcho?\n\nHoncho wins on **user modeling**: it keeps a running picture of who someone is, and that memory follows them across their agent tools.\n\nVectorize (maker of the rival Hindsight) wrote a March 2026 [Hermes memory provider comparison](https://vectorize.io/articles/hermes-agent-memory-providers-compared) that calls it a behavioral model of the user, \"not just a fact store\". Every reason has a catch.\n\n| Reason | Evidence | Catch |\n|---|---|---|\n| It models the person | \"Great on knowing who YOU are\" ([r/hermesagent, May 2026](https://www.reddit.com/r/hermesagent/comments/1tceavu/agentmemory_x_honcho_which_one_is_the_best/)) | `.chat()` is a live LLM call, so each question adds real latency |\n| One memory across tools | Plugins for Claude Code, Codex, Cursor, OpenCode, OpenClaw and Hermes, plus an open-source [MCP server](/en/blog/best-mcp-servers-claude-code), hosted at `mcp.honcho.dev` or self-hosted | Text only for now, with very limited OCR for documents |\n| Accuracy in user tests | A six-provider bake-off on Qwen3.5 4B: Honcho \"performed the best\" ([r/hermesagent, Aug 2026](https://www.reddit.com/r/hermesagent/s/tYlgc1kgAt)) | With the default plugin settings, it used \"almost 3 times the tokens of the next best performer\" |\n| Privacy | Self-hosters cite it ([Elkim, Apr 2026](https://x.com/ElkimXOC/status/2039622200928452642)) | AGPL-3.0 (see cons) |\n\nToken savings are where the marketing runs ahead. The homepage advertises 60-90%, but the [evals page](https://honcho.dev/evals) lists 89% on LongMemEval S, 52% on LoCoMo and 16% on BEAM 100K. A builder quoted on the homepage reports 10-15%.\n\n## Who Uses Honcho, and Who Is It For?\n\n542,206 Python SDK downloads in the month to 28 October 2026 say Honcho has real users, mostly agent builders around Hermes and coding agents.\n\n```stats\ncaption: Adoption signals, retrieved 2026-10-28.\nitems:\n  - value: 542206\n    label: PyPI honcho-ai downloads, last month\n    source: pypistats.org\n  - value: 101791\n    label: npm @honcho-ai/sdk downloads, Sep 27 to Oct 26\n    source: api.npmjs.org\n  - value: 7803\n    label: GitHub stars, 954 forks\n    source: GitHub API\n```\n\nThe homepage labels its logo strip \"Used by developers at\". That means individual developers at these organisations, not company-wide contracts or case studies.\n\n| Group | Examples from honcho.dev |\n|---|---|\n| Enterprises | Microsoft, NVIDIA, GitHub, Cisco, Atlassian, Coinbase |\n| AI teams | OpenRouter, Nous Research, Polymarket, Raycast, Chroma, Hippocratic AI |\n| Research | Stanford, UC Berkeley, Cornell, Johns Hopkins APL, NYU |\n\nNous Research's [Hermes Agent](/en/blog/hermes-agent-v0-15) ships Honcho as a memory plugin (`hermes plugins install honcho`), and the [Hermes Honcho docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho) list five tools, from `honcho_profile` to `honcho_conclude`.\n\nPopularity isn't consensus. A 138-answer Hermes poll on X ([Oct 2026](https://x.com/HermesWatcher/status/2114492238659305561)) put Markdown notes first (27), Hindsight second (25) and Honcho third (22).\n\n- Good fit: companions, tutors and coaching agents\n- Good fit: personal coding agents shared across Claude Code, Codex and Cursor\n- Poor fit: document RAG, next-turn recall, closed-source forks\n\n## Honcho Pros and Cons: What Do You Trade for the Accuracy?\n\nHoncho's accuracy is real; the price is lag, token overhead, a heavy self-host stack and the AGPL, so budget for all four.\n\nSelf-hosting needs Postgres with [pgvector](/en/blog/qdrant-vs-chroma-vs-pgvector), a deriver worker and a tool-calling LLM (the repo's config defaults are `gpt-5.4-mini` and `text-embedding-3-small`). The CLI starts the API, deriver, Postgres and Redis; Docker Compose works too.\n\n```bash\n# .env: set these before starting\nDERIVER_FLUSH_ENABLED=true   # process small batches right away\nAUTH_USE_AUTH=true           # off by default\nAUTH_JWT_SECRET=your-secret  # generate with scripts/generate_jwt_secret.py\n```\n\n```bash\nuv tool install honcho-cli\nhoncho start --setup\n```\n\n### Pros: where Honcho earns its place\n\n- User modeling that developers describe as knowing who you are\n- The strongest long-history result in our recount: +27.8 on LongMemEval S\n- Open source, self-hostable, with plugins for Claude Code, Codex, Cursor, Hermes and more\n\n### Cons: what it costs you\n\n- Lag. Developers report a 9.1 s `minimal` dialectic trace ([#1101](https://github.com/plastic-labs/honcho/issues/1101)) and 2.16 s added to every Hermes API turn ([#1289](https://github.com/plastic-labs/honcho/issues/1289)). The homepage's \"~200 ms\" is a vendor claim about `context()`.\n- Query cost. For 10,000 users adding 20K tokens a month, ingestion is **$400**, but 30 Low-tier queries each is **$3,000** (Minimal: $300). The query tier, not ingestion, decides your Honcho bill.\n- Self-host upkeep and lock-in. You run the API, deriver, Postgres, Redis and an LLM yourself. Moving between cloud and self-hosted means replaying messages, because embeddings aren't exported ([#721](https://github.com/plastic-labs/honcho/issues/721)).\n- AGPL-3.0. One comparison article says self-hosting forces you to release your app's source. That overstates it: [AGPL §13](https://www.gnu.org/licenses/agpl-3.0.html) applies when you modify Honcho and users reach it over a network. Mem0, Letta and cognee are Apache-2.0 and LangMem is MIT, so Honcho is the copyleft outlier among dedicated memory layers. Not legal advice.\n\nRun the quickstart on the $5 credit with one real conversation log before you commit.\n\n## Frequently Asked Questions\n\n### Is Honcho memory free?\n\nPartly. The cloud gives a $5 credit, plus $5 a month with a card, and startups under $5M raised can get $1,000 in credits. Self-hosting has no license fee under AGPL-3.0, but you pay your own LLM and embedding bills.\n\n### Can I use Honcho in a closed-source SaaS?\n\nYes, if your app calls an unmodified Honcho server through its API. If you modify Honcho and serve it over a network, AGPL §13 requires offering that modified Honcho source. Your own app stays closed. Not legal advice; ask counsel if you fork.\n\n### Honcho vs Mem0 or Hindsight: which should I pick?\n\nPick Mem0 (Apache-2.0) for the fastest start, Hindsight (MIT) to save tokens, and Honcho for user modeling. One developer reports Hindsight \"used far fewer tokens\" on Hermes ([X, Oct 2026](https://x.com/StillYazeed/status/2115014740145512772)). Mem0's blog says Honcho lacks public benchmarks, yet it has published 21 raw result files since 2025-12-19. See [the full ranking](/en/blog/best-ai-agent-memory-tools).\n\n```references\ntitle: References\nitems:\n  - title: Honcho Evals\n    publisher: Plastic Labs\n    year: 2025\n    url: https://honcho.dev/evals\n  - title: plastic-labs/honcho README\n    publisher: GitHub\n    year: 2026\n    url: https://github.com/plastic-labs/honcho\n  - title: plastic-labs/honcho-benchmarks\n    publisher: GitHub\n    year: 2025\n    url: https://github.com/plastic-labs/honcho-benchmarks\n  - title: Benchmarking Honcho\n    publisher: Plastic Labs\n    year: 2025\n    url: https://plasticlabs.ai/blog/research/Benchmarking-Honcho\n  - title: Honcho Memory\n    publisher: Nous Research (Hermes Agent docs)\n    year: 2026\n    url: https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho\n  - title: GNU Affero General Public License v3\n    publisher: Free Software Foundation\n    year: 2007\n    url: https://www.gnu.org/licenses/agpl-3.0.html\n  - title: \"LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory\"\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2410.10813\n  - title: Evaluating Very Long-Term Conversational Memory of LLM Agents (LoCoMo)\n    publisher: arXiv\n    year: 2024\n    url: https://arxiv.org/abs/2402.17753\n  - title: ConvoMem\n    publisher: arXiv\n    year: 2025\n    url: https://arxiv.org/abs/2511.10523\n```\n","publishedAt":"2026-10-28T16:06:00.000Z","modifiedAt":"2026-10-28T21:28:05.000Z","readTime":"5 min read","featured":false,"tags":["honcho memory","honcho ai","plastic labs","agent memory","honcho memory review"],"image":{"id":2607,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"alt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","prefix":"techsy-io","updatedAt":"2026-10-28T16:06:29.964Z","createdAt":"2026-10-28T16:06:29.371Z","url":"https://media.techsy.io/techsy-io/hero-789.webp","thumbnailURL":null,"filename":"hero-789.webp","mimeType":"image/webp","filesize":15912,"width":1200,"height":630,"focalX":50,"focalY":50,"sizes":{"small":{"url":"https://media.techsy.io/techsy-io/hero-789-480x252.webp","width":480,"height":252,"mimeType":"image/webp","filesize":4352,"filename":"hero-789-480x252.webp"},"medium":{"url":"https://media.techsy.io/techsy-io/hero-789-720x378.webp","width":720,"height":378,"mimeType":"image/webp","filesize":7268,"filename":"hero-789-720x378.webp"},"full":{"url":"https://media.techsy.io/techsy-io/hero-789-1080x567.webp","width":1080,"height":567,"mimeType":"image/webp","filesize":12604,"filename":"hero-789-1080x567.webp"},"og":{"url":"https://media.techsy.io/techsy-io/hero-789-1200x630.webp","width":1200,"height":630,"mimeType":"image/webp","filesize":15912,"filename":"hero-789-1200x630.webp"}}},"imageAlt":"Honcho memory LongMemEval S score of 90.4%, reproduced in our re-score, over a faint graph of memory nodes","seo":{"metaTitle":"Honcho Memory Review: Pros, Cons and a Re-Scored Benchmark","metaDescription":"Is Honcho memory worth it? Our testing reproduced its 90.4% benchmark score. Here are the pros, cons, real pricing, and who uses it and why, in 2026."},"author":{"id":2,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"name":"Mert Batur","role":"Co-Founder & CTO","image":null,"bio":null,"credentials":[],"linkedinUrl":null,"email":null,"yearsExperience":null,"expertiseAreas":[],"isDefault":false,"legacySanityId":"041ad028-03a0-410a-9629-5425942542ed","updatedAt":"2026-07-29T10:12:55.273Z","createdAt":"2026-07-19T14:25:24.799Z"},"category":{"id":1,"tenant":{"id":1,"name":"Techsy.io","slug":"techsy-io","domain":"techsy.io","defaultLanguage":"en","languages":["en","de","fr","nl","es","it","sv","no","tr","ar"],"rtlLanguages":["ar"],"blogPathByLanguage":[{"id":"6a5cdc06cfc6ef004a4e52b4","language":"sv","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b5","language":"no","path":"blogg"},{"id":"6a5cdc06cfc6ef004a4e52b6","language":"ar","path":"mudawwana"}],"updatedAt":"2026-07-19T14:15:34.820Z","createdAt":"2026-07-19T14:15:34.820Z"},"title":"AI & Machine Learning","slug":"ai-machine-learning","description":null,"legacySanityId":"e5f97163-1d87-4e33-8321-d4b4b74e62c7","updatedAt":"2026-07-19T14:25:22.615Z","createdAt":"2026-07-19T14:15:35.276Z"},"canonicalPost":null,"translationGroup":"honcho-memory-review","sponsored":false,"sponsorUrl":null,"legacySanityId":null,"updatedAt":"2026-10-28T21:28:06.679Z","createdAt":"2026-10-28T16:06:30.352Z","_status":"published"}],"hasNextPage":true,"hasPrevPage":false,"limit":10,"nextPage":2,"page":1,"pagingCounter":1,"prevPage":null,"totalDocs":3871,"totalPages":388}