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

emergent-thinking

v0.2.4

Published

CLI-first local attention engine for project-scoped AI reasoning

Readme

emergent-thinking

emergent-thinking is a project-local skill + CLI for coding agents.

In plain language: it tries to stop the model from improvising everything in its head, and forces it to write the work down, validate against reality, and iterate in loops.

What It Is

emergent-thinking is a local board workflow for AI agents.

It combines:

  • a skills-compatible skill that tells the agent how to work
  • a project-local CLI that stores the board and exposes the protocol

The skill is the working method. The CLI is the external memory and move engine.

This is intentionally not a global MCP memory service. The natural scope is the current repository and its cwd.

Why It Exists

Most coding agents fail in a predictable order:

  1. they form a rough intuition
  2. they start implementing too early
  3. they discover conflicts too late
  4. they patch over the mess
  5. entropy keeps increasing

emergent-thinking tries to change that order.

The core loop is:

  1. write the problem down
  2. write the goal down
  3. choose one bounded path
  4. validate against reality early
  5. record findings and proof debt
  6. repair the cheapest meaningful stage
  7. loop until the board converges

So the promise is not "the model becomes smarter". The promise is "the model is pushed into a more reliable working order".

How To Use

Install it with:

npx emergent-thinking install

or:

bunx emergent-thinking install
pnpx emergent-thinking install

The normal usage is not "manually type lots of CLI commands".

The normal usage is:

  1. install the skill
  2. tell your coding agent to use emergent-thinking
  3. let the skill drive the workflow
  4. let the CLI persist the board inside the current project

If you want the actual operating protocol, read:

If you want contribution, benchmark reproduction, or protocol iteration guidance, read:

Benchmark Snapshot

Latest checked-in protocol_micro summary from evals/inspect_ai:

  • On anthropic/glm-5.1, baseline scored 0.875, sequential scored 0.875, emergent scored 1.0, and emergent_compact also scored 1.0 while using 1,876 fewer total tokens than emergent.

This is not a universal proof. It is one concrete signal that the protocol can improve move ordering, and that prompt compaction can sometimes preserve quality while reducing cost.

Repository Pointers