JSPM

@m3mory/lossless-m3mory-claw

0.2.4
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 20
  • Score
    100M100P100Q95826F
  • License SEE LICENSE IN LICENSE

Lossless m3mory Claw — DAG-based context management with m3mory long-term memory integration for OpenClaw

Package Exports

  • @m3mory/lossless-m3mory-claw
  • @m3mory/lossless-m3mory-claw/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@m3mory/lossless-m3mory-claw) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

lossless-m3mory-claw

Lossless m3mory Claw — A fork of Lossless Claw that integrates m3mory long-term memory into the Lossless Claw context-engine assembly path.

This is the plugin rebuild workstream for the Lossless m3mory Claw runtime. It is not the m3mory commercial dashboard or API service.

What this is

This plugin combines:

  • Lossless Claw — DAG-based context management, incremental compaction, and token-budget assembly (upstream base, MIT licensed)
  • m3mory — Long-term memory retrieval and verified storage, injected as a dynamic context item inside the Lossless Claw assembly path

The result is a context-engine plugin where:

  • m3mory context appears in the assembled prompt as a dynamic, budgeted context item — not as fake conversation history
  • Compaction runs through the lossless path first, not native lossy fallback
  • Compacted material is not released until transfer to m3mory is verified, or a fallback path is explicitly recorded and logged
  • Chatbot, general agent, and coding agent runs receive different context shapes without polluting transcript history

What it does differently from the hook-only plugin

The previous @m3mory/m3moryclaw-plugin used pre-turn and post-turn hooks for recall and capture. That approach worked for basic memory injection but had four gaps:

  1. It did not register as a context engine — Lossless Claw owned assembly, the plugin was a side passenger
  2. It did not own compaction — native lossy compaction could still fire as a fallback
  3. It did not participate in the lossless overflow path
  4. It did not verify transfer before releasing compacted material

This fork fixes all four gaps by extending the Lossless Claw engine base rather than wrapping it from the outside.

Architecture overview

OpenClaw runtime
  └── lossless-m3mory-claw (context-engine)
        ├── Assembly (per turn)
        │     ├── Summaries (DAG, from upstream LCM)
        │     ├── Fresh raw turns (protected tail)
        │     └── m3mory block (dynamic, budgeted)
        │           ├── Retrieved from m3mory API
        │           ├── Shaped by agent type (chatbot / general / coding)
        │           └── Omitted or shrunk under token pressure
        ├── Ingest / capture (write path)
        │     ├── Strip injected m3mory blocks before capture
        │     ├── Apply noise filters
        │     └── Send durable turns to m3mory API
        ├── Compaction (lossless path first)
        │     ├── Transfer to m3mory before release
        │     ├── Verify transfer receipt
        │     └── Log fallback explicitly if verification fails
        └── Diagnostics (/lcm)
              ├── All upstream LCM diagnostics preserved
              └── m3mory retrieval, transfer, and fallback state added

Status

This package is under active development as part of the Lossless m3mory Claw rebuild (Sprint 0 — WP0).

Current sprint: Sprint 0 — Fork foundation and identity (WP0 complete)

Upcoming:

  • WP1: m3mory client and config layer
  • WP2: Unified identity model
  • WP3: Dynamic retrieval in assembly
  • WP4: Agent-type retrieval policy
  • WP5: Capture on the lossless lifecycle
  • WP6: Verified transfer ledger
  • WP7: Continuity index and overflow path
  • WP8: Extended /lcm diagnostics
  • WP9: Manual tools and setup flows
  • WP10: Tests and docs verification

Installation

Install with OpenClaw's plugin installer. This records the install metadata and load path OpenClaw needs for reliable plugin loading, status provenance, and updates.

openclaw plugins install @m3mory/lossless-m3mory-claw@0.2.4

Do not install this package by raw npm install --prefix ~/.openclaw/extensions, by copying files into ~/.openclaw/extensions, or by running npm install inside the extension directory. Those paths can leave OpenClaw without install metadata, which makes the plugin fail to load or appear as drifted/untracked in openclaw status.

For local plugin development, link a working copy through OpenClaw as well:

openclaw plugins install --link /path/to/lossless-m3mory-claw

Configuration

Configuration schema inherits the upstream Lossless Claw options and adds m3mory-specific capture, recall, transfer, and identity settings. See openclaw.plugin.json for the current schema.

Upstream attribution

This package is a fork of Lossless Claw by Josh Lehman / Martian Engineering, used under the MIT License.

The upstream context-engine architecture, DAG summarization, SQLite conversation store, assembly and compaction machinery, and /lcm diagnostics are derived from the Lossless Claw codebase. New work — m3mory API integration, dynamic context injection, verified transfer, identity model, agent-type policy, and diagnostics extensions — is Copyright (c) 2026 m3mory Inc.

See LICENSE for the full licence text and upstream attribution.

Licence

New fork work: Business Source License 1.1 (converts to MIT on 2030-04-20). Upstream Lossless Claw base: MIT. See LICENSE for details.