🧠 lossless-code

DAG-based Lossless Context Management for Claude Code.

Every message preserved forever. Summaries cascade, never delete. Full recall across sessions.

Getting Started · MCP Server · Commands · Terminal UI · How It Works · Configuration · Contributing

The Problem

Claude Code forgets everything between sessions. Existing memory tools (ClawMem, context-memory, context-mode, claude-mem) use flat retrieval-augmented memory: keyword search over stored snippets with no structure, no hierarchy, and no way to drill from a summary back to the original conversation.

When your project spans weeks and hundreds of sessions, flat search breaks down. You get fragments without lineage.

What Makes lossless-code Different

lossless-code uses DAG-based lossless preservation, the same approach pioneered by lossless-claw for OpenClaw:

Nothing is ever deleted. Every message stays in vault.db forever.
Summaries form a directed acyclic graph. Messages become depth-0 summaries, which cascade to depth-1, depth-2, and beyond.
Full drill-down. lcc_expand traces any summary node back to the original messages that created it.
Automatic. Claude Code hooks capture every turn and trigger summarisation transparently. No manual effort.
Cross-session recall. Start a new session and your full project history is immediately searchable and injectable.

                              ┌──────────────────┐
                              │   Claude Code     │
                              │   Session         │
                              └────────┬─────────┘
                                       │
              ┌────────────────────────┼────────────────────────┐
              │                  │                │              │
        ┌─────▼─────┐    ┌──────▼──────┐  ┌──────▼──────┐ ┌────▼─────┐
        │  Hooks     │    │   Skills    │  │   CLI       │ │  MCP     │
        │  (write)   │    │  (shell)    │  │   Tools     │ │  Server  │
        │            │    │             │  │             │ │  (stdio) │
        │ SessionStart│   │ lcc_grep    │  │ lcc_status  │ │          │
        │ Stop       │    │ lcc_expand  │  │             │ │ 6 tools  │
        │ PreCompact │    │ lcc_context │  │             │ │ read-only│
        │ PostCompact│    │ lcc_sessions│  │             │ │          │
        │ UserPrompt │    │ lcc_handoff │  │             │ │          │
        └─────┬──────┘    └──────┬──────┘  └──────┬──────┘ └────┬─────┘
              │                  │                │              │
              └──────────────────┼────────────────┼──────────────┘
                                 │                │
                        ┌────────▼────────────────▼──┐
                        │         vault.db            │
                        │         (SQLite)            │
                        │                             │
                        │  messages    summaries       │
                        │  summary_sources  sessions   │
                        │  FTS5 indexes                │
                        └──────────────────────────────┘

Install

Option A: Claude Code Plugin (recommended)

/plugin marketplace add GodsBoy/lossless-code
/plugin install lossless-code

Hooks, MCP server, and skill are activated automatically. No manual setup needed.

Option B: Standalone Install

git clone https://github.com/GodsBoy/lossless-code.git
cd lossless-code
bash install.sh

The installer:

Creates ~/.lossless-code/ with vault.db and scripts
Configures Claude Code hooks in ~/.claude/settings.json
Installs the skill to ~/.claude/skills/lossless-code/
Adds CLI tools to PATH

Idempotent: safe to run again to upgrade.

Requirements

Python 3.10+
SQLite 3.35+ (for FTS5)
Claude Code CLI

Optional: anthropic Python package for AI-powered summarisation (falls back to extractive summaries without it).

MCP Server

lossless-code includes an MCP (Model Context Protocol) server so Claude Code can access the vault as native tools without shelling out to CLI commands.

Setup

The installer (install.sh) automatically:

Copies the MCP server to ~/.lossless-code/mcp/server.py
Installs the mcp Python SDK
Registers the server in ~/.claude.json

After installation, every new Claude Code session auto-discovers 6 MCP tools:

Tool	Description
`lcc_grep`	Full-text search across messages and summaries
`lcc_expand`	Expand a summary back to source messages (DAG traversal)
`lcc_context`	Get relevant context for a query
`lcc_sessions`	List sessions with metadata
`lcc_handoff`	Generate session handoff documents
`lcc_status`	Vault statistics (sessions, messages, DAG depth, DB size)

Manual Registration

If you need to register the MCP server manually:

// ~/.claude.json
{
  "mcpServers": {
    "lossless-code": {
      "command": "python3",
      "args": ["~/.lossless-code/mcp/server.py"]
    }
  }
}

Architecture

  Claude Code  ──stdio──▶  MCP Server  ──read-only──▶  vault.db
                            (server.py)
                            6 tools

The MCP server is read-only. All writes to the vault happen through hooks (SessionStart, Stop, UserPromptSubmit, PreCompact, PostCompact). The MCP server imports db.py directly for SQLite access.

Commands

`lcc_grep <query>`

Full-text search across all messages and summaries.

lcc_grep "database migration"
lcc_grep "auth refactor"

`lcc_expand <summary_id>`

Expand a summary node back to its source messages.

lcc_expand sum_abc123def456
lcc_expand sum_abc123def456 --full

`lcc_context [query]`

Surface relevant DAG nodes for a query. Without a query, returns highest-depth summaries.

lcc_context "auth system"
lcc_context --limit 10

`lcc_sessions`

List recorded sessions with timestamps and handoff status.

lcc_sessions
lcc_sessions --limit 5

`lcc_handoff`

Show or generate a session handoff.

lcc_handoff
lcc_handoff --generate --session "$CLAUDE_SESSION_ID"

`lcc_status`

Show vault statistics: message count, summary count, DAG depth, and FTS index health.

lcc_status

Terminal UI (lcc-tui)

lcc-tui is a terminal-based browser for your vault. Built with Textual.

lcc-tui

Views

Tab	Key	Description
Sessions	`1`	Browse all sessions — select to view messages
Search	`2`	Full-text search across messages and summaries
Summaries	`3`	Browse DAG summaries by depth — select to expand
Stats	`4`	Dashboard: sessions, messages, summaries, vault size

Navigation

1–4 — switch tabs
/ — open search modal from any view
Enter — drill into selected session or summary
Esc — go back
q — quit

Full reference: docs/tui.md

How It Works

Hooks (Automatic)

Hook	Event	Purpose
`session_start.sh`	SessionStart	Register session, inject handoff + summaries
`stop.sh`	Stop	Persist each turn to vault.db
`user_prompt_submit.sh`	UserPromptSubmit	Surface relevant context for the prompt
`pre_compact.sh`	PreCompact	Run DAG summarisation before compaction
`post_compact.sh`	PostCompact	Record compaction, re-inject top summaries

DAG Summarisation

Collect unsummarised messages, chunk into groups of ~20
Summarise each chunk (via Claude API or extractive fallback)
Write summary nodes to summaries table (depth=0)
Link to sources in summary_sources
Mark source messages as summarised
If depth-N exceeds threshold: cascade to depth-N+1
Repeat until under threshold at every depth

Storage

~/.lossless-code/
  vault.db       # SQLite: all messages, summaries, DAG, sessions
  config.json    # Settings (summary model, thresholds)
  scripts/       # Python modules and CLI tools
  hooks/         # Shell scripts called by Claude Code hooks

Configuration

~/.lossless-code/config.json:

{
  "summaryModel": "claude-haiku-4-5-20251001",
  "chunkSize": 20,
  "depthThreshold": 10,
  "incrementalMaxDepth": -1,
  "workingDirFilter": null
}

Key	Default	Description
`summaryModel`	`claude-haiku-4-5-20251001`	Model for summarisation
`chunkSize`	`20`	Messages per summary chunk
`depthThreshold`	`10`	Max nodes at any depth before cascading
`incrementalMaxDepth`	`-1`	Max cascade depth (-1 = unlimited)
`workingDirFilter`	`null`	Only capture messages from this directory

Schema

sessions      -- session_id, working_dir, started_at, last_active, handoff_text
messages      -- id, session_id, turn_id, role, content, tool_name, working_dir, timestamp, summarised
summaries     -- id, session_id, content, depth, token_count, created_at
summary_sources -- summary_id, source_type, source_id
messages_fts  -- FTS5 index on messages.content
summaries_fts -- FTS5 index on summaries.content

Comparison

	lossless-code	ClawMem	context-memory	claude-mem
Storage	SQLite with FTS5	SQLite + vector DB	Markdown files	SQLite + Chroma
Structure	DAG (summaries cascade)	Flat RAG retrieval	Flat retrieval	Flat retrieval
Drill-down	Full (summary to source messages)	None	None	None
Auto-capture	Hooks (zero manual effort)	Hooks + watcher	Manual	Hooks + worker
Cross-session	Yes (vault persists)	Yes	Yes	Yes
Summarisation	Cascading DAG (depth-N)	Single-level	None	Single-level
Search	FTS5 full-text	Hybrid (BM25 + vector + reranker)	Keyword	Hybrid (BM25 + vector)
MCP tools	6	28	0	10+
Background services	None	watcher + embed timer + GPU servers	None	Worker on port 37777
Runtime	Python (stdlib)	Bun + llama.cpp (optional)	None	Bun
Models required	None (optional for summarisation)	2GB+ GGUF (embed + reranker)	None	Chroma embeddings
Idle cost	Zero	CPU/RAM for services + embedding sweeps	Zero	Worker process

Why lossless-code Costs Less

Memory tools that inject context on every prompt are silently expensive. Here's why lossless-code's design saves tokens:

1. On-demand recall, not automatic injection

ClawMem injects relevant memory into 90% of prompts automatically (their stated design). claude-mem injects a context index on every SessionStart. Both approaches front-load tokens whether or not the agent needs that context.

lossless-code injects nothing by default. Context surfaces only when the agent explicitly calls an MCP tool or the PreCompact hook fires. Most coding turns (writing code, running tests, reading files) don't need historical context at all. You pay for recall only when recall matters.

2. Fewer MCP tool definitions = fewer tokens per turn

Every MCP tool registered in ~/.claude.json has its schema injected into every single API call as available tools. Claude Code's own docs warn: "Prefer CLI tools when available... they don't add persistent tool definitions."

ClawMem: 28 MCP tools (query, intent_search, find_causal_links, timeline, similar, etc.)
claude-mem: 10+ search endpoints via worker service
lossless-code: 6 MCP tools (grep, expand, context, sessions, handoff, status)

Over a 200-turn session, that difference in tool schema overhead compounds significantly.

3. No background embedding costs

ClawMem runs a watcher service (re-indexes on file changes) and an embed timer (daily embedding sweep across all collections). These require GGUF models (~2GB minimum) and consume CPU/GPU continuously. claude-mem runs a persistent worker service on port 37777.

lossless-code has zero background processes. Hooks fire only during Claude Code events. The vault is pure SQLite with FTS5 (built into SQLite, no external models). There's nothing running between sessions.

4. DAG summarisation reduces compaction waste

When Claude Code hits its context limit, it compacts: summarising earlier context to make room. With flat memory systems, compaction loses fidelity and the agent may re-explore territory it forgot, costing more tokens ("debugging in circles").

lossless-code's DAG captures the full conversation before compaction happens (PreCompact hook). After compaction, the PostCompact hook re-injects only the top-level summaries. The agent can drill down via lcc_expand if it needs detail, but the DAG ensures nothing is truly lost. This means:

Fewer repeated explorations after compaction
One long session is cheaper than multiple short sessions covering the same ground
Context survives compaction without paying to re-read everything

5. No runtime dependencies

Dependency	lossless-code	ClawMem	claude-mem
Python 3.10+	Yes (usually pre-installed)	No	No
Bun	No	Required	Required
llama.cpp / GGUF models	No	Optional (2GB+)	No
Chroma / vector DB	No	No	Required
systemd services	No	Recommended	No
`mcp` Python SDK	Yes (pip install)	No (TypeScript)	No

Fewer dependencies = less to maintain, fewer failure modes, less resource consumption.

Uninstall

rm -rf ~/.lossless-code
# Remove hooks from ~/.claude/settings.json manually
# Remove skill: rm -rf ~/.claude/skills/lossless-code

Prior Art and Acknowledgements

lossless-code is a Claude Code adaptation of the Lossless Context Management (LCM) architecture created by Jeff Lehman and the Martian Engineering team. Their lossless-claw plugin for OpenClaw proved that DAG-based context preservation eliminates the information loss problem in long-running AI sessions. lossless-code brings that same architecture to Claude Code.

Additional references:

ClawMem by yoloshii (hooks architecture patterns)
Voltropy LCM paper (theoretical foundation)

Contributing

Contributions are welcome! Please:

Fork the repository
Create a feature branch (git checkout -b feat/your-feature)
Write tests for new functionality
Ensure tests pass
Open a pull request

Roadmap

lossless-code currently supports Claude Code natively. The hook and plugin ecosystem across coding agents is converging fast, and we're tracking compatibility:

Agent	Hook Support	MCP	Status	Notes
Claude Code	20+ lifecycle events	✅	✅ Supported	Full plugin with hooks, MCP, skills
Copilot CLI	Claude Code format	✅	🟢 Next	Reads `hooks.json` natively; lowest adaptation effort
Codex CLI	SessionStart, Stop, UserPromptSubmit	✅	🟡 Planned	Experimental hooks engine (v0.114.0+); MCP works today
Gemini CLI	BeforeTool, AfterTool, lifecycle	✅	🟡 Planned	Different event names; needs thin adapter layer
OpenCode	session.compacting + plugin hooks	✅	🔵 Researching	Plugin architecture differs; compacting hook maps to PreCompact

MCP works everywhere today. Any agent that supports MCP servers can already use lcc_grep, lcc_expand, lcc_context, lcc_sessions, lcc_handoff, and lcc_status for manual recall. The roadmap above tracks automatic capture via hooks.

Contributions welcome for any of the planned integrations.

Star History

Contributors

Licence

MIT

If lossless-code helps your workflow, consider giving it a ⭐

Report Bug · Request Feature

Name		Name	Last commit message	Last commit date
Latest commit History 17 Commits
.claude-plugin		.claude-plugin
docs		docs
hooks		hooks
mcp		mcp
scripts		scripts
skills/lossless-code		skills/lossless-code
tests		tests
tui		tui
.gitignore		.gitignore
.mcp.json		.mcp.json
LICENSE		LICENSE
README.md		README.md
install.sh		install.sh

Folders and files

Latest commit

History

Repository files navigation

🧠 lossless-code

The Problem

What Makes lossless-code Different

Install

Option A: Claude Code Plugin (recommended)

Option B: Standalone Install

Requirements

MCP Server

Setup

Manual Registration

Architecture

Commands

lcc_grep <query>

lcc_expand <summary_id>

lcc_context [query]

lcc_sessions

lcc_handoff

lcc_status

Terminal UI (lcc-tui)

Views

Navigation

How It Works

Hooks (Automatic)

DAG Summarisation

Storage

Configuration

Schema

Comparison

Why lossless-code Costs Less

1. On-demand recall, not automatic injection

2. Fewer MCP tool definitions = fewer tokens per turn

3. No background embedding costs

4. DAG summarisation reduces compaction waste

5. No runtime dependencies

Uninstall

Prior Art and Acknowledgements

Contributing

Roadmap

Star History

Contributors

Licence

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0