@pinchpass/cli1.2.1

@pinchpass/cli

One-time E2E-encrypted secret request links for AI agents.

Generate a temporary HTTP server with a single-use encrypted form for collecting sensitive values (API keys, tokens, passwords) — locally or over the internet via a built-in bore.pub tunnel. The relay never sees the secret: encryption happens in the browser, and the decryption key lives only in the URL fragment.

Install

npm i -g @pinchpass/cli     # provides the `pinchpass` command

npx @pinchpass/cli request API_KEY   # no install; fetches the binary on first run

brew install --cask rubybear-lgtm/tap/pinchpass

The npm package installs this package's bin/pinchpass.js, which resolves the platform binary and hands off to it. The postinstall downloads that binary to ~/.local/bin, verifying it against the release's checksums.txt, and is version-aware: when the binary it finds (on PATH, or in ~/.local/bin, ~/.openclaw/bin, ~/.pi/bin) does not report the package's version, it downloads the matching release asset and replaces it. Set PINCHPASS_SKIP_DOWNLOAD=1 to skip the download.

Updating

pinchpass --version                           # pinchpass v1.2.0 (abc1234)
npm update -g @pinchpass/cli                  # re-runs the postinstall
brew upgrade --cask pinchpass
go install github.com/rubybear-lgtm/pinchpass@latest

The extension warns when the binary it resolves is older than the package.

Pi (pi.dev)

This package is a native Pi package:

pi install npm:@pinchpass/cli

That registers:

• request_secret tool — two collection modes:
  • via: "modal" (default in the TUI): a Pi dialog collects each secret directly into .env — the value never reaches the LLM, never enters the transcript, and no server is started. Cancelable with Esc. ttl does not apply here and is ignored.
  • via: "link": spawns the CLI, streams the one-time E2E-encrypted link to the user immediately, blocks until they submit or the TTL expires. The URL (including its #k= decryption-key fragment) is shown to the model and stays in the transcript, so prefer the modal when the secret is sensitive.
  • via defaults to "auto": modal in the TUI, link everywhere else.
  • tunnel: true always uses the link, even in the TUI — the modal cannot serve a remote user.
• pinchpass skill — full usage guidance for the model.

The binary is resolved from PATH, ~/.local/bin, ~/.openclaw/bin, and ~/.pi/bin — no PATH configuration required (not needed for the modal mode).

OpenClaw

Installed as a plugin, it registers the same request_secret tool. Note that the OpenClaw path executes the CLI in the foreground: keep the exec timeout longer than the TTL, or the link dies with the exec session.

CLI

pinchpass request <secret-name>... [flags]

License

MIT