LongMemory
CaviraOSSLongMemory is a self-hosted memory engine that records what an agent learns as an immutable, time-stamped graph of entities, claims and relationships, then recalls it in strict, historical or associative modes within a token budget. One TypeScript engine runs as a library, CLI, HTTP and MCP server, dashboard and VS Code extension. CaviraOSS builds it, and it was previously published as OpenMemory.
Read against the repository's main branch, which holds the rewritten Hydrograph engine; the longmemory package on npm still ships the earlier OpenMemory code under the new name.
Openness
5 high confidence- license
- Apache-2.0 (engine, CLI, server, dashboard, Python client and agent integrations)+MIT (n8n community node)
- source
- public
- core features withheld
- no — the 566-path tree at aec98ce carries the root Apache-2.0 LICENSE and per-integration Apache-2.0 or MIT files, with no ee/, enterprise/, commercial/ or proprietary/ path; the README offers no hosted edition or paid tier
LongMemory's engine, server, clients and integrations are published under permissive licenses, and the README presents the whole system as local-first and self-hosted, built from source or run from the published container. Nothing in the repository or its documentation describes a hosted edition or a paid feature held back from the code.
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/integrations/n8n-nodes-longmemory/LICENSE recorded 2026-11-20
The n8n node carries its own MIT License, "Copyright (c) 2026 CaviraOSS and nullure".
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/LICENSE recorded 2026-11-20
The root LICENSE is the Apache License 2.0 text, ending "LongMemory: Durable Memory Engine for AI Systems / Copyright 2026 CaviraOSS and nullure".
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/package.json recorded 2026-11-20
The manifest names the package longmemory, "license": "Apache-2.0", repository CaviraOSS/LongMemory, and describes it as "library, CLI, self-hosted API server, and benchmark harness".
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/README.md recorded 2026-11-20
The README calls LongMemory "Local-first and self-hosted", builds and starts the service "From source" with pnpm or runs ghcr.io/caviraoss/longmemory, and says the Python package is an HTTP client while "The Hydrograph engine remains in the self-hosted TypeScript service".
- https://raw.githubusercontent.com/CaviraOSS/OpenMemory/main/README.md recorded 2026-11-20
The old CaviraOSS/OpenMemory path serves the LongMemory README byte for byte, so the repository was renamed rather than replaced.
Adoption
1 low confidenceAdoption is read from npm downloads of longmemory, the package the README installs. The legacy openmemory-js package, the container image and the VS Code extension are not counted, and the published package carries the earlier OpenMemory engine rather than the current one.
- https://api.npmjs.org/downloads/point/last-month/longmemory recorded 2026-11-20
135 downloads of longmemory between 2026-10-20 and 2026-11-18.
- https://registry.npmjs.org/longmemory recorded 2026-11-20
The registry entry lists one version, 1.3.3, authored by caviraoss, whose readme installs longmemory and links the license to CaviraOSS/LongMemory.
Capability
5 medium confidenceLongMemory performs every part of the cycle itself, including retiring a fact once a later statement supersedes it and keeping the old one for historical questions. Its extraction is rule-based rather than model-driven, which keeps ingest deterministic but reads less from a conversation than the language-model pipelines of Memori or ReMe.
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/docs/consolidation.md recorded 2026-11-20
Consolidation "converts clusters of raw episodic memories into higher-order semantic, procedural, reflective, or corrected grounded memories", linking each to its sources.
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/docs/entities.md recorded 2026-11-20
The entity resolver merges only under high confidence, creates merge candidates when uncertain and records semantic drift as a new edge instead of overwriting.
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/docs/ingest.md recorded 2026-11-20
Ingest step 3 parses "entities, claims, preferences, actions, procedures, emotions, reflections"; a changed preference creates "new --supersedes--> old" and "The handler closes the old valid-time and marks it superseded."
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/docs/temporal.md recorded 2026-11-20
Every durable fact is stored bitemporally; strict recall "uses only current truth, so superseded facts are excluded", while historical recall can still reach them.
- https://raw.githubusercontent.com/CaviraOSS/LongMemory/main/README.md recorded 2026-11-20
The README lists "Temporal truth: recorded time and valid time are separate", "Lifecycle: deterministic decay, explicit reinforcement, consolidation, compression, and reconsolidation" and strict, historical, associative and world-grounded recall modes.
Verified 2026-11-20, except some scores, still awaiting re-confirmation