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

@habemus-papadum/aiui-devtools-extension

v0.3.0

Published

Chrome DevTools panel for aiui — monitor the channel server, the websocket transport, and lowering traces.

Vulnerabilities

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

Links

Git

Maintainers

lilinjnlilinjn

Keywords

Readme

@habemus-papadum/aiui-devtools-extension

A Chrome DevTools panel for debugging the aiui infrastructure. Published to npm with the built extension inside (extension/, including its compiled js/), so aiui installed as a dependency can auto-load it — into the browser it is always loaded unpacked (there's no store listing). Design doc: the repo's DevTools Panel guide page.

Four views over two data sources:

| Tab | Shows | Source | | --- | ----- | ------ | | Server | The channel server's identity (tag, port, pid, owning Claude session), how the launcher wired the session (Chrome DevTools MCP on/off, attach endpoint or lazy launch, browser + profile — the connectivity-debugging view), health-ping latency, and server-side transport counters (connections, frames, bytes, per-frame processing time). | GET /debug/api/info, /debug/api/stats on the channel server | | Transport | The page's view of the websocket: per-frame sizes and ack round-trip latency, with avg/p50/p95. | window.__AIUI__ instrumentation recorded by aiui-dev-overlay, read via chrome.devtools.inspectedWindow | | Traces | The prompt-lowering trace debugger (inputs → IRs → lowered prompt). | The server's /debug page, embedded (still usable standalone) | | Intent | One chosen trace, live-followed: the multimodal intent event stream, the recomputed IR passes (timeline → transcript + corrections → lowered Option-C prompt with token→path meta), and per-segment timing — rendered through the shared debug-ui module. Works for any trace (text-concat renders generically); intent-v1 traces get the rich event view. | GET /debug/api/traces + the /debug/api/traces/:id/live revision poll |

The Intent pane

Pick a trace and it follows it live — a one-second poll of /debug/api/traces/:id/live, which answers {unchanged:true} when nothing moved (the revision is the manifest's mtime), so following a running lowering is a trickle of bytes, not an open socket. The rendering is the same debug-ui the workbench lab uses, so intent debugging looks identical in both homes.

Port discovery is the same as the other tabs: the inspected page's window.__AIUI__.port is primary; failing that, the panel falls back to the most recently used port (remembered in localStorage, offered on the manual field's datalist) and the manual field always overrides. If the launcher's OpenAI-key preflight reported a non-valid status (surfaced under /debug/api/info → launch.openaiKey, a status only — never the key), the pane shows one line explaining that transcription and correction are unavailable until the key is set or fixed (the mock backends are the offline alternative). With no channel or an unreachable one, it says so quietly and does nothing else.

Beyond the panel, the extension stamps tab identity onto dev pages (localhost / 127.0.0.1): whenever such a tab finishes loading, the background worker assembles the tab's ids — chrome.tabs id/window/index plus the CDP target id from chrome.debugger.getTargets() (no attach, so it never disturbs another debugger) — and injects a one-liner that writes them to data-aiui-tab on <html>. The intent tool ships that stamp with every submission, which is how a lowered prompt can tell the agent which browser tab it came from (see the repo's Web Intent Tool guide and the session-browser skill). Internals — the mechanism, why it injects from the background rather than using a content script, and the permission/debugging gotchas — are in this package's Tab Identity guide (docs/tab-identity.md).

Install (unpacked)

pnpm --filter @habemus-papadum/aiui-devtools-extension build   # tsc → extension/js

Then Chrome → chrome://extensions → enable Developer mode → Load unpacked → select packages/aiui-devtools-extension/extension. Open DevTools on a page running the intent tool and pick the aiui tab.

The session browser (the shared Chrome that aiui claude or aiui browser starts) rebuilds this extension in a dev checkout every time the browser starts (~0.3 s of tsc — never stale; disable with chrome.buildExtension: false in config) and gets it auto-loaded (--load-extension) where the browser honors that flag — Chromium and Chrome for Testing do, Chrome-branded builds ≥ 137 ignore it. Where it's ignored, do the unpacked install above once in that browser (aiui chrome extension prints the directory); its profile (.aiui-cache/chrome/<profile>) keeps it across sessions.

The panel discovers the channel port from the inspected page (window.__AIUI__.port, published when the intent tool mounts). No instrumented page? A manual port field appears — and the panel also works opened as a plain tab (panel.html?port=<port>), minus the page-side Transport metrics.

Notes

  • extension/js/ is build output (gitignored); manifest.json and the HTML shells are source.
  • The extension's manifest.json version is independent of the workspace's lockstep version (Chrome requires plain dotted integers).
  • The Intent pane renders through the shared debug-ui, which lives in aiui-dev-overlay. tsc can't bundle that package's (bundler-mode) source into a browser file, so the full build (pnpm --filter … build) runs an extra esbuild step — build-debug-ui.mjs — that bundles @habemus-papadum/aiui-dev-overlay/debug-ui (from source, no overlay build step) into extension/js/debug-ui.js, which the panel imports lazily. The session browser's launch-time auto-rebuild is tsc-only, so in a fresh dev checkout the Intent pane degrades (with a hint) until pnpm build produces that bundle once; every other tab works regardless. Published tarballs ship it prebuilt.