npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pixelguild/loom

v0.1.8

Published

Session intelligence layer for Claude Code — persistent memory, intelligent archiving, cross-project patterns, and peer LLM consultation.

Downloads

497

Readme


Loom is an MCP server that gives Claude Code a long-term memory. It logs what Claude does, archives context when it grows large, and lets Claude pick up exactly where it left off in the next session.

Install

npm install -g @pixelguild/loom
loom init

This scaffolds docs/loom/, wires the MCP server into .claude/mcp.json, and adds instructions to your CLAUDE.md. That's it.

Or add manually:

claude mcp add loom -- loom serve

What it does

| Feature | Description | |---------|-------------| | Context logging | Structured entries (decisions, actions, issues, questions) appended to docs/loom/context.md | | Session pickup | Claude reads context at session start and resumes where it left off | | Intelligent archiving | Spawns a Claude subprocess to produce narrative archives with rolling carry-forward summaries | | Pattern library | Global SQLite store with FTS5 search — save solutions in one project, find them everywhere | | Peer consultation | Ask OpenAI, Vertex AI, or Ollama for a second opinion on architecture, debugging, or design | | Execution manifests | Save structured plans for headless claude runs | | Per-project config | Customize thresholds, providers, and settings via loom.config.json |

How it works

Session start                          Session end
     |                                      |
     v                                      v
 loom_get_context  -->  Claude works  -->  loom_log_context
     |                  with full           |
     |                  history             v
     v                                 Token threshold?
 Resume where                          Yes --> loom_archive_context
 you left off                                  |
                                               v
                                         Narrative archive with
                                         carry-forward summary

The latest archive's carry-forward summary + current context.md always gives Claude full project history without reading every old archive.

MCP Tools

| Tool | Purpose | |------|---------| | loom_get_context | Read current context. Call at session start. | | loom_log_context | Log a structured entry (action, decision, issue, question, dead_end, session_end) | | loom_get_session_status | Token count, archive count, threshold status | | loom_archive_context | Archive context (intelligent with Claude subprocess, mechanical fallback) | | loom_save_pattern | Save a reusable pattern to the global library | | loom_find_pattern | Search patterns across all projects | | loom_create_manifest | Save a structured execution manifest | | loom_get_manifest | List or retrieve manifests | | loom_consult_peer | Ask a peer LLM for a second opinion |

CLI

loom init      # Scaffold project, wire MCP, inject CLAUDE.md
loom status    # Token count, archive status, context health
loom serve     # Start MCP server (called by Claude Code automatically)

Configuration

Layered config — per-project overrides global defaults.

Global ~/.loom/config.json:

{
  "default_provider": "openai",
  "providers": {
    "openai": { "model": "gpt-4o" },
    "vertex": { "model": "gemini-2.0-flash", "project": "my-gcp-project", "location": "us-central1" },
    "ollama": { "model": "llama3.1", "host": "http://localhost:11434" }
  }
}

Per-project docs/loom/loom.config.json:

{
  "archive_thresholds": { "warning": 40000, "archive": 50000 },
  "peer_consultation": { "enabled": true, "allowed_providers": ["openai", "ollama"] }
}

| Variable | Purpose | |----------|---------| | LOOM_PROJECT_ROOT | Project directory (falls back to cwd) | | LOOM_OPENAI_API_KEY | OpenAI API key for peer consultation |

Peer Consultation Setup

The loom_consult_peer tool lets Claude ask a second LLM for architecture advice, debugging help, or alternative perspectives.

OpenAI — Set LOOM_OPENAI_API_KEY env var or pass it via MCP config:

claude mcp add loom -e LOOM_PROJECT_ROOT=$(pwd) -e LOOM_OPENAI_API_KEY=sk-... -- loom serve
{ "default_provider": "openai", "providers": { "openai": { "model": "gpt-4o" } } }

Vertex AI (Gemini) — Requires gcloud auth application-default login:

{ "default_provider": "vertex", "providers": { "vertex": { "model": "gemini-2.0-flash", "project": "your-gcp-project", "location": "us-central1" } } }

Ollama (local) — No API key needed. Install Ollama and pull a model:

{ "default_provider": "ollama", "providers": { "ollama": { "model": "llama3.1", "host": "http://localhost:11434" } } }

Restrict providers per project in docs/loom/loom.config.json:

{ "peer_consultation": { "enabled": true, "allowed_providers": ["openai", "ollama"] } }

Storage

docs/loom/
  context.md              # Active session context
  loom.config.json        # Per-project config (optional)
  archives/
    2026-03-08-001.md     # Timestamped narrative archives
  manifests/
    deploy-plan.md        # Execution manifests

~/.loom/
  config.json             # Global config
  loom.db                 # SQLite pattern library (FTS5)

License

MIT © Pixel Guild, LLC