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

@carter-mcalister/pi-worktrunk

v0.4.1

Published

Worktrunk-backed worktree extension for Pi Coding Agent

Readme

@carter-mcalister/pi-worktrunk

Worktrunk-backed worktree management for Pi Coding Agent.

This extension keeps a familiar /worktree ... command surface inside Pi, but it now delegates worktree behavior to Worktrunk instead of calling git worktree directly.

What changed

pi-worktrunk is now a thin wrapper around wt:

  • /worktree createwt switch --create --no-cd
  • /worktree listwt list --format=json
  • /worktree removewt remove
  • /worktree status / /worktree cd use wt list --format=json

The extension no longer reads ~/.pi/agent/pi-worktrees-settings.json.

Runtime behavior now comes from Worktrunk config files:

  • user config: ~/.config/worktrunk/config.toml
  • project config: .config/wt.toml

Install

1. Install the Pi extension

pi install npm:@carter-mcalister/pi-worktrunk

2. Install Worktrunk

macOS / Linux (Homebrew):

brew install worktrunk

Or follow the upstream install instructions:

  • https://worktrunk.dev/worktrunk/
  • https://github.com/max-sixty/worktrunk

3. Install Worktrunk shell integration

wt config shell install

4. Create Worktrunk config

User config:

wt config create

Project config:

wt config create --project

If Pi is already running, use /reload after installing the extension.

Quick start

In Pi:

/worktree init
/worktree create feature/auth-refactor
/worktree list
/worktree status
/worktree cd feature/auth-refactor
/worktree remove feature/auth-refactor

Command reference

| Command | Behavior | | --- | --- | | /worktree init | Show Worktrunk setup guidance | | /worktree settings | Show Worktrunk config info via wt config show | | /worktree create <branch> | Create a worktree via Worktrunk | | /worktree list | List worktrees and optionally switch via Worktrunk | | /worktree status | Show the current worktree from Worktrunk JSON output | | /worktree cd <name> | Print the matching worktree path | | /worktree remove <name> | Remove a worktree via Worktrunk | | /worktree prune | Deprecated; use Worktrunk-native cleanup flows | | /worktree templates | Deprecated; use Worktrunk template docs |

Aliases retained:

  • /worktree ls/worktree list
  • /worktree rm/worktree remove
  • /worktree config/worktree settings
  • /worktree vars / /worktree tokens/worktree templates

Configuration

This extension does not maintain its own runtime config anymore.

Use Worktrunk config instead:

User config

~/.config/worktrunk/config.toml

Example:

worktree-path = "{{ repo_path }}/.worktrees/{{ branch | sanitize }}"

[projects."github.com/org/repo"]
worktree-path = ".worktrees/{{ branch | sanitize }}"

Project config

.config/wt.toml

Example:

[pre-start]
deps = "bun install"

[post-start]
editor = "zellij action new-tab --name {{ branch | sanitize }} --cwd {{ worktree_path }}"

[list]
url = "http://localhost:{{ branch | hash_port }}"

See Worktrunk docs for full configuration:

  • https://worktrunk.dev/config/
  • https://worktrunk.dev/hook/
  • https://worktrunk.dev/switch/
  • https://worktrunk.dev/list/
  • https://worktrunk.dev/remove/

Removed extension-owned features

The Worktrunk-backed version intentionally drops behavior that duplicated Worktrunk:

  • ~/.pi/agent/pi-worktrees-settings.json
  • repo pattern matching / matching strategies
  • extension-managed onCreate, onSwitch, onBeforeRemove
  • extension-managed branch generators
  • /worktree create --generate
  • /worktree create --name
  • extension template preview for custom hook variables

If you used those features before, migrate them to Worktrunk config and hooks.

Notes

  • This extension expects wt to be installed and available on PATH.
  • Pi keeps the /worktree command surface, but Worktrunk is now the source of truth.
  • For directory switching in your shell, Worktrunk shell integration is still required.

Credits

This package is a maintained fork of @zenobius/pi-worktrees.

Credit to Zenobius for the original project and foundation this fork builds on.

Development

mise install
bun install
mise run check