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

@akalsey/sapience-thinking

v0.2.0

Published

Your agent notices things. While it works, it watches for anomalies, patterns, and opportunities that don't fit neatly into scheduled tasks — the kind of "I noticed this while doing something else" observations that a thoughtful colleague would flag. Ever

Readme

OpenClaw Thinking

Your agent notices things. While it works, it watches for anomalies, patterns, and opportunities that don't fit neatly into scheduled tasks — the kind of "I noticed this while doing something else" observations that a thoughtful colleague would flag. Every 15 minutes during working hours, it runs a brief thinking pass over recent activity, produces a structured list of observations and proposed actions, and surfaces anything worth your attention.

The output is a reviewable log file, not autonomous action. You see what it noticed, you decide what to do with it.

This plugin is part of the Sapience Suite that gives your OpenClaw agent genuine agency — not just the ability to execute tasks, but the judgment to know when to act, when to ask, when to propose, and when to say "I'm not sure how you want me to handle this."

This plugin can be used without Sapience if all you want to do is surface observations to the human.

Setup

Install

openclaw plugins install npm:@akalsey/sapience-thinking

Configuration

Add to your OpenClaw config:

{
  "plugins": {
    "sapience-thinking": {
      "schedule": "*/15 * * * *",
      "activeHours": {
        "start": "08:00",
        "end": "20:00",
        "timezone": "America/Los_Angeles"
      },
      "output": {
        "logPath": "~/.openclaw/proactive-thinking/thinking-log.md"
      }
    }
  }
}

All settings are optional — the defaults above are used if omitted.

Output files

| File | Purpose | |------|---------| | ~/.openclaw/proactive-thinking/thinking-log.md | Human-readable log of every pass | | ~/.openclaw/proactive-thinking/outcomes.json | Tracks which proposals you acted on | | ~/.openclaw/proactive-thinking/proposals.jsonl | Structured sidecar read by sapience |


What a pass looks like

Each entry in thinking-log.md has:

  • Observations — things noticed with supporting evidence and priority (1–5)
  • Proposed actions — concrete things to do, with estimated effort
  • Proposed audits — domains worth reviewing
  • Open questions — things blocking analysis
  • Summary — one-paragraph overview

A pass that found nothing useful logs nothing_to_report: true. Over time, this data shows when thinking passes are productive.


Active hours

Passes only fire within activeHours. Outside that window, the cron fires but silently skips — no log entry. Set the window to match your working hours.


Troubleshooting

Nothing in the log after install The plugin fires on cron schedule, not immediately. Wait for the next 15-minute boundary, or manually trigger:

openclaw cron run sapience-thinking-pass

Passes are running but log is empty Check that logPath is writable and that the path (including ~) is resolving correctly. Try an absolute path first.

Too many proposals, too much noise The signal-to-noise data in outcomes.json feeds back into future prompts after 14 days. Mark proposals as acted-on or dismissed to train the signal:

openclaw thinking resolve <proposal-id> acted_on
openclaw thinking resolve <proposal-id> dismissed

nothing_to_report on every pass This usually means the context bundle is too thin — no recent session activity to analyze. The plugin needs active use of OpenClaw to have something to think about.