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

@datspike/pi-fork-resume

v0.1.0

Published

Pi extension that forks a session selected through the resume-style session picker without opening the source session.

Readme

@datspike/pi-fork-resume

Pi extension that forks a session selected through the resume-style session picker without opening the source session.

Why

Pi already has useful primitives:

  • pi --fork <path|id> safely forks a session, but only at process startup.
  • /resume has the right global session picker, but opens the selected session as the active file.
  • /fork forks the current active session from a selected message.

This package fills the gap: choose any existing session from the resume picker, copy it into a new fork for the current project, and switch to that fork.

Install

pi install npm:@datspike/pi-fork-resume

For local development:

pi -e /home/spike/hobby/pi-fork-resume

Commands

/fork-resume

  1. Waits until the current agent turn is idle.
  2. Opens the same session picker component used by /resume.
  3. Lets you choose a session from the current project or all projects.
  4. Creates a new session via SessionManager.forkFrom(sourcePath, ctx.cwd, ctx.sessionManager.getSessionDir()).
  5. Switches to the newly created fork via ctx.switchSession(forkedFile).

The selected source session is not resumed and is not opened as the active session.

/fork-picker

Alias for /fork-resume.

Current /fork limitation

The intended long-term UX is to make /fork open the resume-style picker. In Pi 0.70.6, built-in interactive commands are handled before extension commands, and /fork is hardcoded to the current-session message picker. A package-level extension cannot safely override that behavior.

This extension deliberately avoids monkey patching Pi internals. When Pi exposes built-in command override hooks or changes command priority, the implementation can register /fork as a thin alias to the same workflow.

Development

npm install
npm run check

The architecture keeps Pi wiring thin:

  • src/index.ts registers commands and adapts Pi APIs.
  • src/fork-resume.ts contains the testable workflow.
  • src/session-label.ts contains fallback selector formatting helpers.
  • tests/*.test.ts cover cancellation, fork errors, switch cancellation, and option formatting.

Release

npm version patch
npm publish --access public

The package is published as a Pi package through the pi.extensions manifest in package.json.