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

harnessd

v0.2.0

Published

A multi-surface coding agent daemon: sessions, tools, processes, and MCP over JSON-RPC on a WebSocket.

Readme

harnessd

A long-lived coding-agent daemon. It owns the model loop, sessions, tools, and managed processes, and speaks JSON-RPC 2.0 over a WebSocket so any number of thin clients (CLI, TUI, web, or another agent over MCP) can attach to the same session at once.

npx harnessd
# [harnessd] listening on ws://127.0.0.1:7777 (pid 12345)

What it does

  • Sessions — each is a conversation thread with its own history, working directory, tool policy, memory scratchpad, and context budget. Persisted as JSONL under ~/.harness/sessions, so a restart loses nothing.
  • Tools — read, write, edit, bash (foreground or background), memory, and task (spawn a sub-agent, optionally on a different model).
  • Processes — background commands are supervised, logged to disk, and survive daemon restarts; killable as a group.
  • MCP — connects to MCP servers listed in ~/.config/mcp/mcp.json (stdio and streamable HTTP) and offers their tools to the model. Deferred loading plus a tool-search tool keeps large tool catalogs out of the context window.
  • Context — cross-turn tool history, lossless tool-result eviction, and summarizing compaction, in that order.

Configuration

Credentials: ANTHROPIC_API_KEY, or HARNESS_PROVIDER=vertex with HARNESS_VERTEX_PROJECT and Google application default credentials.

| Env | Default | Meaning | | --- | --- | --- | | HARNESS_PORT / HARNESS_HOST | 7777 / 127.0.0.1 | Listen address | | HARNESS_PROVIDER | anthropic | anthropic or vertex | | HARNESS_MODEL | claude-sonnet-4-6 | Default model (per-session override) | | HARNESS_EFFORT | high | Reasoning effort; clamped per model | | HARNESS_THINKING | adaptive | hidden keeps thinking, drops the transcript; off disables | | HARNESS_CACHE | on | Prompt-cache breakpoints | | HARNESS_MCP_CONFIG | ~/.config/mcp/mcp.json | MCP config file(s), colon-separated; off disables | | HARNESS_TOOL_SEARCH | on | Defer MCP tool schemas behind a search tool | | HARNESS_SESSIONS_DIR | ~/.harness/sessions | Session logs | | HARNESS_WEB_DIR | unset | Also serve a web UI from this directory |

The daemon binds loopback and has no authentication of its own; put a tunnel with real auth in front if you want it reachable.

Status

Early. The protocol is stable enough to build on but not frozen.

Requires Node >= 22.