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

llm-wb

v0.1.0-beta.5

Published

A portable chat harness for governed agentic development workflows.

Downloads

643

Readme

llm-workbench

Turns AI coding conversations into isolated, reproducible Git workspaces.

llm-workbench is a standalone, provider-neutral Git/Bash/npm chat harness for blank or existing repos.

Run AI coding sessions in isolated git worktrees without dirtying main.

Why use it?

AI coding tools are useful, but they make it easy to lose context, mix unrelated changes, or pollute your main branch.

llm-workbench gives every chat session its own branch, worktree, and session log so you can experiment safely and merge only when ready.

Before LLM-Workbench

  • one long AI conversation trying to solve multiple problems
  • random commits
  • forgot why code changed
  • dirty main
  • abandoned branches

After LLM-Workbench

Main
    │.                         │
    ▼.                         ▼
Start chat #1.            Start chat #n
    │.                         │
    ▼.                         ▼
Create worktree/branch.       ...
    │
    ▼
Code with AI
    │
    ▼
Checkpoint
    │
    ▼
Continue tomorrow
    │
    ▼
Merge back to main
  • one branch per AI session
  • session logs
  • isolated worktrees
  • merge when ready

Quick start

Public npm install is the intended user path:

cd /path/to/your/repo

npx llm-wb init --dry-run
npx llm-wb init

If your repo already has workbench files from an earlier manual copy or bootstrap, start with adoption instead:

npx llm-wb@latest adopt --dry-run
npx llm-wb@latest adopt --apply

Then start and inspect work from that repo:

npx llm-wb new "your prompt here"  // creates new chat session with prompt; happens automatically if you start a chat in code-assistant
npx llm-wb sessions list // lists open chat sessions
npx llm-wb commit -m "Describe the completed work" // ask chat to commit - runs gates and checks
npx llm-wb merge-main  // merges to local main, handles conflict

llm-wb list lists installed workbench commands. To list active chat sessions, use llm-wb sessions list.

This installs into your target repo:

  • Adds the llm-wb CLI
  • Configures AGENTS.md
  • Installs workbench scripts
  • Enables safe uninstall
  • Writes .llm-workbench/lock.json and .llm-workbench/manifest.json
  • Creates session logs that preserve decisions, prompts and commit history.

Update to the latest published workbench with a dry run first:

npx llm-wb@latest update --dry-run
npx llm-wb@latest update --apply

Roll back or test an older published version by pinning the package:

npx [email protected] update --dry-run
npx [email protected] update --apply

Updates only replace files recorded as workbench-managed in .llm-workbench/manifest.json. Files such as commitLogs/, product code, branches, worktrees, and repo-specific layers are left alone. If a managed file was changed locally, update stops with a conflict instead of overwriting it.

Each new llm-chat session then creates:

  • a chat-owned branch
  • a git worktree for that branch
  • a session log/checkpoint record
  • merge-readiness checks before promotion back to main

Works with existing repositories. No migration required. Uninstall removes only files owned by LLM Workbench.

Who is this for?

Developers using Claude Code, Codex, Cursor or Copilot coding assistants who want safer multi-session repo workflows.

Security Boundaries

  • does not push to remote
  • does not rewrite history
  • does not delete branches without approval
  • does not overwrite locally changed managed files
  • does not require a specific LLM provider