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

wienerdog

v0.9.0

Published

Give your AI a memory, habits, and a daily routine — with nothing but files. One-line setup for Claude Code and Codex CLI.

Readme

Wienerdog 🌭🐕

Give your AI a memory, habits, and a daily routine — with nothing but files.

You already pay for a great AI model. Wienerdog makes it feel dramatically smarter — not by changing the model, but by installing the right files around it: a real profile of you, a persistent markdown memory, skills for your recurring tasks, and a nightly "dreaming" process that learns from your conversations.

curl -fsSL https://raw.githubusercontent.com/wienerdog-ai/wienerdog/main/install.sh | bash

On Windows, open PowerShell and run:

irm https://raw.githubusercontent.com/wienerdog-ai/wienerdog/main/install.ps1 | iex

Prefer npm? npx wienerdog@latest init does the same thing on any OS. Either script checks for Node (and git); if either is missing it offers to install it for you — always asking first and showing the exact command it will run, and simply printing that command for you to run yourself if you decline or aren't in an interactive terminal. On Windows, installing Node this way may pop up a one-time admin (UAC) prompt — that's Windows asking permission, not Wienerdog; decline it and you get the same command to run yourself instead. The window stays open and tells you when it's done. Read install.sh or install.ps1 first if you like; once Node is ready either one hands over to the versioned npm package. That handoff doesn't pause for another confirmation — it prints its plan as it installs, and running the one-liner is your go-ahead. Want to review the plan before anything is written? Run npx wienerdog@latest init --dry-run first, or use the AI-assisted install below.

Windows has full parity: vault, skills, and scheduled nightly dreaming all work — the nightly dream registers in Task Scheduler for your own user (no admin rights), and if the machine was off or asleep at dream time it catches up after you're back.

Not comfortable with the terminal at all? Paste the prompt below into Claude Code or Codex and your AI will install Wienerdog for you. In this flow you are the approval step: it shows you the plan first, installs only after you say go, and points you at the metadata so a cautious AI can confirm the package is genuine before running it.

Please install Wienerdog for me. It's an open-source tool that gives an AI a
memory and daily routines using plain files. Before running anything, you can
verify it: GitHub https://github.com/wienerdog-ai/wienerdog, npm
https://www.npmjs.com/package/wienerdog. Then:
1. Show me the plan: run `npx wienerdog@latest init --dry-run` and summarize what
   it would create. Wait for me to say go ahead.
2. Install it: run `npx wienerdog@latest init --yes`.
3. Tell me to restart Claude Code (or Codex) so the new Wienerdog skills
   load — they only appear after a restart.
4. After I restart, walk me through the Wienerdog setup.

After the restart, in Claude Code:

/wienerdog-setup

In Codex CLI, skills start a little differently: type /skills to see them, then $wienerdog-setup — or just ask for "Wienerdog setup" in plain words.

That's it. Your AI interviews you, builds your memory vault, and starts remembering.

Status: 0.x. Installable and dogfooded daily by its maintainer; file formats may still evolve until 1.0 (the installed file layout is our public API).

What you get

  • A proper CLAUDE.md / AGENTS.md — generated from an interview, not a blank page. Your AI knows who you are, how you work, and what you care about, in every session.
  • A markdown memory vault — Obsidian-convention PARA structure (works with Obsidian if you use it, doesn't require it). Plain files you own, readable by you, versioned in git.
  • Dreaming — a nightly job reviews the day's conversations, promotes what matters into long-term memory through quality gates, and turns your repeated workflows into reusable skills. Skills Wienerdog created keep learning: the dream watches how they perform in real use and revises them over time — your own skills and Wienerdog's built-ins are never touched (see the threat model). Every night is at most one git commit; anything can be reverted. If your computer is off or asleep at that time, don't worry — Wienerdog catches up automatically the next time you're back.
  • Google Workspace senses (optional) — Gmail, Calendar, and Drive access that is read-first and draft-first by design. Your AI can only send what you explicitly granted, to recipients you explicitly approved — grants are created by you at the keyboard, never by the AI.
  • Laptop-friendly routines (optional, pick from a catalog) — after setup, choose from a menu of ready-made scheduled routines (morning digest, inbox triage, weekly review, …) run by your OS's native scheduler (launchd / systemd / Task Scheduler). Laptop was closed at run time? It catches up. No daemon.

Why Wienerdog and not a "personal AI agent" app?

Projects like OpenClaw and Hermes are impressive — and they are applications: gateways, daemons, servers you must run, secure, and update. Wienerdog is different by design:

Wienerdog is just files. Markdown, skills, hooks, config — interpreted by the AI tool you already run and trust. No new long-running software: nothing listens, nothing serves, nothing phones home. No extra hardware, no VPS. And because everything executes through your own Claude Code / Codex subscription, you stay fully within your provider's terms of service.

Built by its own product

This repo dogfoods Wienerdog from day one: its own memory vault lives in memory/, its development conventions are its own CLAUDE.md, and most of its code is written by mid-tier AI models following its spec system (see docs/specs/). The product thesis — an AI gets dramatically better when you install the right files around it — is also how this project is built.

Documentation

License

MIT