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

forge-codex-connector

v0.1.3

Published

Outbound host bridge for managed Codex app-server control through codex-bus-mcp.

Readme

forge-codex-connector

Outbound host bridge for a private local codex app-server.

Usage

npx forge-codex-connector connect \
  --api https://your-public-host.example \
  --token "$CODEX_BUS_CONNECT_TOKEN" \
  --mcp-token "$CODEX_BUS_HTTP_TOKEN" \
  --name user-a-worker-1 \
  --cwd /home/user-a

If --api is omitted, it defaults to https://bus.noagi.cloud.

The bridge starts codex app-server --listen ws://127.0.0.1:<free-port>, connects to it locally, then opens an outbound WebSocket to codex-bus-mcp. For --api https://your-public-host.example, it derives:

  • control WebSocket: wss://your-public-host.example/connect
  • MCP URL injected into threads: https://your-public-host.example/mcp

Requirements

  • Node.js 20 or newer.
  • A working codex binary in PATH, or --codex-bin /path/to/codex.
  • A reachable codex-bus-mcp control plane with /connect enabled.

Options

  • --api: public control plane base URL, default https://bus.noagi.cloud.
  • --id: optional stable id for this connector process, default random.
  • --token: host enrollment token matching CODEX_BUS_CONNECT_TOKEN.
  • --mcp-url: optional override for the derived public HTTP MCP URL.
  • --mcp-token: optional HTTP MCP token.
  • --mcp-name: injected MCP server name, default codex-agents.
  • --name: host display name.
  • --cwd: working directory for the child codex app-server.
  • --codex-bin: Codex executable, default codex.
  • --app-server-host: local bind host, default 127.0.0.1.
  • --app-server-port: local bind port, default is a free port.

Environment

  • FORGE_CODEX_CONNECTOR_API
  • FORGE_CODEX_CONNECTOR_ID
  • FORGE_CODEX_CONNECTOR_TOKEN
  • FORGE_CODEX_CONNECTOR_CODEX_BIN
  • FORGE_CODEX_CONNECTOR_MCP_URL
  • FORGE_CODEX_CONNECTOR_MCP_TOKEN
  • FORGE_CODEX_CONNECTOR_MCP_NAME

Legacy CODEX_APP_CONNECTOR_* names are also accepted as aliases.

MCP Auto-Config

The connector derives the MCP URL from --api so new and resumed threads can receive the public HTTP MCP config. --mcp-token is optional; when present, the bridge passes it to the child codex app-server as FORGE_CODEX_CONNECTOR_MCP_HTTP_TOKEN and injects bearer_token_env_var into each thread config. --mcp-name defaults to codex-agents.

Security

The child app-server binds to 127.0.0.1 by default. The only public connection is the outbound WebSocket to the control plane.