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

@autosk/feature-dev-docker

v0.1.0

Published

feature-dev-docker — the @autosk/feature-dev (pi) cycle with every agent step running in a per-task dockerSandbox (ghcr.io/wierdbytes/pi-runtime), authenticated with the host ~/.pi.

Readme

@autosk/feature-dev-docker

The Docker variant of @autosk/feature-dev: the same dev → review → docs → validator → accept (human) → cleanup → done pi cycle, but every agent step runs inside a per-task docker run -i --rm container (ghcr.io/wierdbytes/pi-runtime) instead of on the host.

It reuses featureDevWorkflow() verbatim — bounce-backs (review→dev, validator→dev), the dev visit-cap, and the cleanup teardown step — only swapping the default worktreeSandbox() for a credential- and git-aware dockerSandbox. It registers ONE workflow, feature-dev-docker.

How it works

  • Thin image, host MCP. Under a dockerSandbox (sandbox.thin === true) @autosk/pi-agent mints a per-session host HTTP MCP server and injects only the ack-only autosk_transit tool. The transport-aware @autosk/pi-tools (loaded from the mounted ~/.pi) POSTs autosk_task/autosk_comment to that server over host.docker.internal — so the image needs neither autosk nor a mounted daemon socket.
  • Auth. pi keeps its provider tokens in ~/.pi/agent/auth.json (a portable file), so the host ~/.pi is bind-mounted at the container's /home/agent/.pi (read-write). No export step.
  • Git. dockerSandbox bind-mounts only the per-task git worktree; a worktree's .git points into <projectRoot>/.git/worktrees/<id>, so this package also bind-mounts the project .git at its identical path (layered in at wrap() time) so in-container git/go/make resolve the repo.

Use it

# 1. build (or pull) the pi-runtime image
daemon/extensions/pi-agent/docker/build.sh

# 2. install this extension + restart the daemon
autosk ext add npm:@autosk/feature-dev-docker     # or: autosk ext add /path/to/feature-dev-docker

# 3. enroll a task
autosk enroll <task-id> --workflow feature-dev-docker

Env knobs (all optional):

| var | default | what | |-----|---------|------| | AUTOSK_PI_DOCKER_IMAGE | ghcr.io/wierdbytes/pi-runtime:latest | image to run | | AUTOSK_PI_DIR | ~/.pi | host pi config (auth + models) bind-mounted into the container |

Exports

  • default — the extension factory (registers feature-dev-docker).
  • defaultDockerImage() / featureDevDockerSandbox() — for composing your own workflow over the same docker sandbox.