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

openstoat

v0.3.0

Published

AI and Human task queue - orchestrate work between AI agents and humans with a local-first CLI

Readme

OpenStoat

AI ↔ Human task queue — orchestrate work between AI agents and humans with a local-first CLI.

npm version


Who should read what

This README is written for humans. If you're a human and want to quickly understand what OpenStoat is and how to use it, read this.

openstoat --help is written for AI agents. If you're an AI agent, use openstoat --help (and openstoat manual) for the full operational guide — task commands, workflows, and rules.


What is OpenStoat?

OpenStoat is a decoupled task queue that coordinates AI agents and humans. AI handles tasks that don't require human input; when humans complete their tasks, downstream AI tasks are triggered automatically. No cloud, no API keys, no built-in LLM — just a local SQLite store and a CLI.

  • Local-first: All data in ~/.openstoat/ (SQLite)
  • 1 human + N agents: Humans are the bottleneck; AI fills idle time
  • Transparent: Clear task states, dependencies, and handoffs

Install

npm install -g openstoat

1. Initialize a project

How:

openstoat project init --id my_project --name "My Project" --template checkout-default-v1

Why: Every task belongs to a project. You must create a project before agents can create or work on tasks. The project ID (my_project) is used in all task commands.


2. Install skills in your OpenClaw project

How: In your OpenClaw project directory (where you run OpenClaw as Agent Planner):

openstoat install skill --here

This installs planner and worker skills to the current directory (./openstoat-planner, ./openstoat-worker).

Why: OpenClaw (or other agents) need these skills to know how to use OpenStoat — creating tasks, claiming, executing, handing off. Without them, the agent won't know the CLI workflow. Use OpenClaw as your Agent Planner because it has memory and timer features that help with planning over time.


3. Start the daemon

How:

openstoat daemon init   # First time: interactively create .openstoat.json
openstoat daemon start  # Start the daemon

Run these from your project source root (where your code lives and where .openstoat.json will be created).

What it does: The daemon polls for ready tasks owned by agent_worker. When it finds one, it invokes your configured agent (e.g. Cursor CLI, Claude Code) with the task prompt. The agent then claims the task, implements it, and marks it done. One task per poll; the daemon keeps running.

Why: So your coding agents can pick up work automatically without you manually triggering them. Configure the agent path in .openstoat.json — recommend Claude Code or Cursor CLI for coding tasks.


4. Start the Web UI

How:

openstoat web
# Opens http://localhost:3080

Why: To view the Kanban board and monitor task progress.

Recommendation: For interacting with OpenStoat (e.g. marking your human tasks done), use an agent in project x0 instead of the web UI. Create a dedicated project x0 for human tasks. When you finish your work, tell the agent in x0 that you're done and ask it to run openstoat task done <task_id> for your task. The agent handles the CLI; you just talk to it.


Requirements

  • Node.js 22+ or Bun
  • No account or API key required

Links


License

MIT