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

@mgravey/loom-companion-codex-experimental

v0.2.0

Published

Experimental website client for routing Loom Codex model requests through the Loom.js Companion Chrome extension.

Downloads

171

Readme

@mgravey/loom-companion-codex-experimental

Experimental website client for the published Loom.js Companion Chrome extension. It requests explicit approval for the calling website origin, exposes the extension-backed Loom authentication provider, and routes credential-free Codex model request bodies through an external Chrome port. Access tokens, account routing, provider headers, and the upstream request remain extension-owned.

pnpm add @mgravey/loom-core \
  @mgravey/loom-agent-codex \
  @mgravey/loom-coding \
  @mgravey/loom-model-codex-experimental \
  @mgravey/loom-companion-codex-experimental
import { createCodexCompanion } from '@mgravey/loom-companion-codex-experimental';
import { createCodexExperimentalModel } from '@mgravey/loom-model-codex-experimental';

const companion = createCodexCompanion({
  runtime: chrome.runtime,
  sessionId: 'website-session',
});

await companion.ensureOriginAccess();

const model = createCodexExperimentalModel({
  model: 'gpt-5.6-sol',
  wireProtocol: 'responses-lite',
  transport: companion.transport,
});

For rejected upstream responses, the extension sends only a validated status and bounded providerCode, providerMessage, retryable, and retryAfterMs values. The Companion validates and re-sanitizes every field before exposing it to the model adapter. It never exposes the complete provider body, response headers, credentials, or arbitrary error objects.

The same credential-free transport accepts operation: 'compact'. The extension validates the separate compaction envelope and routes it only to /backend-api/codex/responses/compact; it never accepts a caller-provided endpoint.

The default extension ID is gdcebopdllcifgleoefgbobdopiaholg. Production callers must use HTTPS, and the extension user must approve the exact website origin. Local development is limited to localhost and 127.0.0.1. The extension protocol and Codex-compatible provider integration remain unsupported experiments; do not describe them as an official OpenAI authentication or API.

Licensed under MPL-2.0.