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

omp-wiretap

v0.2.0

Published

Raw LLM network request inspector for oh-my-pi (omp)

Readme

wiretap

npm version npm downloads

Raw LLM network request inspector for oh-my-pi (omp).

Captures every provider request the session sends — the exact JSON body that goes on the wire — plus the paired response status, headers, and time-to-first- byte, and renders them as an in-transcript inspector card.

wiretap demo

Install

# npm — also listed in the pi.dev package catalog
omp plugin install omp-wiretap

# or from the marketplace repo
omp plugin marketplace add luobochuanqi/omp-extensions
omp plugin install wiretap@omp-extensions

# or once, from a checkout
omp --extension /path/to/omp-extensions/wiretap

# or persistent: ~/.omp/agent/config.yml
extensions:
  - /path/to/omp-extensions/wiretap

# or as a linked plugin (uses the omp.extensions manifest)
cd /path/to/omp-extensions/wiretap && omp plugin link .

No dependencies to install at runtime — the extension imports only host- provided @oh-my-pi/* modules. (bun install is dev-only, for typecheck and the render preview.)

Usage

| Command | Effect | | --- | --- | | /wire | List captured requests (chronological; newest last) | | /wire <n> | Detail card: endpoint, status/ttfb, response headers, syntax-highlighted JSON body | | /wire dump <n> [path] | Export a body to a file (default wiretap-<n>.json in cwd) | | /wire clear | Truncate this session's capture store | | /wire help | Usage notes |

Collapsed cards show the last 8 requests / first 40 body lines; the global tool-output expansion toggle shows the rest (up to 600 persisted lines). Beyond that, /wire dump exports the full body.

What is captured

  • Request body — the provider payload after all host transforms (before_provider_request), i.e. the exact JSON sent: system prompt, messages, tools, thinking config, images. Inline strings longer than 240 (base64 images especially) render elided with their true size; the stored body and /wire dump keep everything up to the 8 MB body cap.
  • Response metadata — HTTP status, all response headers, request id, and time-to-first-byte (after_provider_response, fired before the stream body is consumed).
  • Endpoint identity — provider, transport api, model, and base URL from the request's resolved model.

Request headers (auth, user-agent) are constructed below the host's extension seam and are not exposed; the body is the wire payload itself.

Storage

Captures persist with the session: every request/response pair is appended to wiretap/<session-id>.ndjson in the session's artifacts directory, so /wire history survives /resume and process restarts. Sequence numbers continue across resumes. The session id in the file name matters: subagents adopt the parent's artifacts directory but report their own session id, so each writer owns its own file instead of interleaving into one.

Consecutive request bodies are nearly identical on the wire — the history is append-only most of the time — so each record stores only the changed region (line delta) against the previous body, with a full body every 32nd record so reconstruction stays bounded. Records whose delta would not shrink the line are stored in full; bodies are reconstructed on demand for /wire <n> and /wire dump. Payloads that do diverge (compaction, model or tool switches, moving cache markers) automatically fall back to full records — a stored body reproduces its capture byte-for-byte (bodies over the 8 MB cap are stored clipped, flagged as such in the detail view).

/wire clear truncates the store. Storage grows with the conversation (the same order as the transcript itself); there is no record-count cap. Sessions started with --no-session have no store and keep the last 32 bodies (24 MB budget) in memory instead.

Response pairing is newest-open: a session serializes its provider requests, so the newest unpaired capture owns the next response. Concurrent streams in one process (advisors, subagents) can cross-wire status/timing; bodies stay exact.

Development

bun install
bun run typecheck   # tsc --noEmit against pinned @oh-my-pi/* types
bun run selfcheck   # drives the factory with a mock ExtensionAPI; asserts capture/pairing/delta storage/resume persistence/views
bun run preview     # renders sample list/detail/note cards against the real dark theme
bun preview.ts 80   # preview at a specific terminal width

Record the demo GIF with vhs (runs a real session — uses your configured model/credentials):

vhs < demo.tape