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

@xudesheng/pto-gui

v0.5.6

Published

Native PTO Topic workbench for Windows x64 and macOS arm64.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

xudeshengxudesheng

Keywords

Readme

PTO GUI

Native Topic workbench for Windows x64 and macOS arm64. Install with npm install -g @xudesheng/pto-gui, then run pto-gui or pto-gui --topic /absolute/path/topic.toml.

The GUI package depends on exactly the same version of @xudesheng/pto and its native platform package. Installing the CLI alone does not install the GUI. The launcher resolves the selected PTO package and its platform dependency using Node's module resolver, including nested installations. It passes the native absolute path to the workbench; no npm shim is used as an owned backend.

PTO_BIN overrides the bundled backend and must name an absolute native executable. Invalid overrides and damaged/version-mismatched packages do not silently fall back. Standalone GUI binaries may also discover native PTO on PATH; shell/npm shims are rejected by the workbench.

The launcher exits after OS process creation. The GUI owns and stops its PTO backend; closing the window does not leave that workflow running. Launcher success does not certify GUI initialization. Startup errors are recorded in pto-gui-startup-*.log and crashes in pto-gui-crash-*.log under the system temporary directory. A missing platform package or executable asks you to reinstall PTO GUI. pto-gui -V prints the GUI package version. macOS ships a bare arm64 executable.

Open a user-maintained Topic, choose its working directory and starting participant, review feedback/oneshot settings, then Start. Follow live logs and acknowledged task/round/force stop controls. Version 0.5.0 adds runtime messages: choose recipients, add a PROMPT to the queue, withdraw pending deliveries, recover drafts and inspect read-only run history. Pending deliveries remain in acceptance order; completed history has separate paging. Prompts and output retain their original language; application labels use English. The embedded flame-loop icon appears in the workbench and native application identity.

PTO GUI first shipped in v0.4.0. An explicit backend override must provide PTO 0.4.0 or later and the compatible control handshake. The bundled backend is matched to the installed GUI version automatically.

Log location

Default logs and relative log_dir start at the Topic file's checkout root, independent of the task's execution worktree. PTO resolves the Topic's real path and checks its directory plus at most four parents for a .git file or directory. If none is found, it uses the workflow launch directory (the GUI's Launch directory for GUI runs). Absolute log_dir is used unchanged. The rule is the same for direct and npm installs; existing logs and message history are not moved.