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

@ctxpilot/ctxpilot

v0.1.1

Published

Auto-builds and injects project context into every AI tool you use

Readme

ctxpilot

CI ko-fi

ctxpilot is a CLI and MCP server that keeps a living project summary in .ctxpilot/context.md. It updates that summary from your repo and gives the same starting context to Claude Code, Codex CLI, Cursor, and Windsurf.

Demo story

Open a fresh Codex session and ask about a cart bug. With ctxpilot set up, Codex can answer about cart.ts line numbers cold because it already read the LCD and has the project MCP tools available.

Install

npm install -g @ctxpilot/ctxpilot

Set CK_PROVIDER and the matching API key in a project .env or ~/.ctxpilot/.env before ctx init.

One-off run:

npx @ctxpilot/ctxpilot init

Quickstart

ctx init
ctx setup
ctx watch

ctx init creates .ctxpilot/ and the first LCD. ctx setup wires MCP and native instruction files. ctx watch starts the background updater.

Command reference

| Command | What it does | Notes | | --- | --- | --- | | ctx init | Create .ctxpilot/ and build the first LCD | Prompts for provider, goal, stack, and preferences | | ctx setup | Write MCP config for installed clients and project instruction files | Supports Claude Code, Codex CLI, Cursor, and Windsurf | | ctx watch [--since <timeframe>] | Start the background watcher | Runs ctx update after changes | | ctx update [--since <timeframe>] | Run one incremental update now | --since accepts 2h, 1d, 1w, or an ISO date | | ctx build | Rebuild the LCD from the current repo state | Archives the previous LCD | | ctx show [--raw] [--json] | Print the current LCD | --raw prints markdown, --json prints metadata and content | | ctx inject --format <markdown|xml|plaintext> | Output the current LCD for prompts | Default format is markdown | | ctx signal <text> | Add a manual signal for the next update | Writes to .ctxpilot/signals.json | | ctx serve | Start the MCP server for the current project | Used by MCP client configs |

How auto-update works

  • ctx watch starts a daemon and writes .ctxpilot/daemon.pid.
  • The daemon watches project files, .git/refs/heads, and .ctxpilot/signals.json.
  • Changes are debounced for 30 seconds, then ctx update runs.
  • .ctxpilot/ output files are ignored so updates do not trigger themselves.

MCP setup

Run ctx setup inside the project you want to expose. It writes a project MCP server name like ctx-my-project.

| Client | Home config written by ctx setup | Project file written by ctx setup | | --- | --- | --- | | Claude Code | ~/.claude/claude_desktop_config.json | CLAUDE.md | | Codex CLI | ~/.codex/config.toml | .agents/skills/ctxpilot/SKILL.md | | Cursor | ~/.cursor/mcp.json | .cursor/rules/ctxpilot.mdc | | Windsurf | ~/.windsurf/mcp.json | .windsurf/rules/ctxpilot.md |

If a client directory is not installed, ctx setup skips its home config. CLAUDE.md is always managed because it is a plain project file.

Support

If ctxpilot saves you time, consider supporting development:

Contributing

ctxpilot is open source and PRs are welcome. See CONTRIBUTING.md for local setup and contribution rules, and docs/MASTERPLAN.md for the full roadmap.