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

planalot

v0.1.1

Published

Lightweight local plan conversation daemon and browser UI for agent planning workflows.

Readme

planalot

A local plan workspace daemon and browser UI for agent planning workflows.

⚠️ Experimental — early phase. Planalot is in an experimental, pre-1.0 stage. The CLI commands, HTTP API, on-disk plan format, and overall behavior may change without notice between releases, and breaking changes can land in any version. Not yet recommended for production use.

Install

Install the CLI globally from npm:

npm install -g planalot

Then wire Planalot into your agent harness:

# For Claude Code
planalot install cc

# For Codex
planalot install codex

# For Pi
planalot install pi

Stack

  • Node.js 22+ native HTTP daemon
  • TypeScript ESM packages
  • Vite + React single-file browser app
  • SSE for live session updates
  • pnpm workspaces

Quick start

pnpm install
pnpm build
printf '# Plan\n' > PLAN.md
pnpm planalot PLAN.md

The CLI starts or reuses a per-user daemon, creates a Planalot-owned workspace under ~/.planalot/plans/<id>, and opens the browser UI. Imported files are copied into Planalot; Planalot owns the source of truth after creation/import.

Plan workspaces

Each plan is stored as:

~/.planalot/plans/<id>/
  manifest.json
  feedback.json
  requirements/
    index.md
  design/
    architecture.md
    flow.html
  tasks/
    tasks.md

requirements/index.md is required and canonical. Additional .md and .html files live under requirements/, design/, or tasks/.

Useful CLI commands:

pnpm planalot create --name "Payments Plan" --json
pnpm planalot import PLAN.md --name "Payments Plan" --json
pnpm planalot find payments --status planning --json
pnpm planalot read <planId> --all --json
pnpm planalot write <planId> design/architecture.md --stdin --json
pnpm planalot open <planId>
pnpm planalot wait-feedback <planId> --timeout 600 --json
pnpm planalot feedback-result <planId> --stdin --json
pnpm planalot implement <planId> --json

Pi install

pnpm planalot install pi

Then restart Pi or run /reload. The Pi extension provides /planalot <existing-plan.md> and the planalot_open_plan tool.

Claude Code install

pnpm planalot install cc

This installs ~/.claude/skills/planalot/SKILL.md. If an older generated ~/.claude/commands/planalot.md exists, the installer updates it as a fallback, but Claude Code prefers the skill. In Claude Code, use /planalot to create, import, review, or continue Planalot-owned layered plan workspaces.

To check whether the generated Claude Code skill matches the local Planalot CLI version:

pnpm planalot install cc --check

Codex install

pnpm planalot install codex
codex plugin add planalot@personal

Then start a new Codex thread and use $planalot. The Codex plugin opens Planalot from the current workspace, but feedback from the browser is manual/copyable until Codex exposes a live extension message bridge like Pi's sendUserMessage.

To check whether the generated Codex plugin, generated skill, Codex cache, and local Planalot CLI version are in sync:

pnpm planalot install codex --check

License

Apache-2.0. See LICENSE and NOTICE.