wolfy-j/codex-lb

A personal, native Wippy provider for routing requests through owner-operated Codex accounts.

[!WARNING] Personal-use only. This package is designed for one owner operating their own installation and accounts. It is not recommended or supported for multi-user, team, shared-subscription, credential-sharing, or hosted-service environments.

codex-lb adds Codex Personal Pool to a Wippy host's model-provider catalog. It keeps account credentials in a private host filesystem and exposes the standard wippy.llm provider and generator contracts, so hosts such as Kickside and Bee can use it without a proxy, listener, or sidecar.

What it provides

• A wippy.llm:provider / wippy.llm:generator binding at wolfy_j.codex:provider.
• A provider-profile editor for configuring a pool of isolated Codex account caches.
• Deterministic account selection, hard continuation affinity, and serialized OAuth refresh per account.
• Redacted account allowance, credit, and usage snapshots for host dashboards.
• A safe streaming Responses transport. Authentication failover is possible only before a response starts and only for a definite HTTP 401; quota, rate-limit, payment, and ambiguous failures are never retried on another account.

Installation and configuration

Install wolfy-j/codex-lb from the Wippy Hub through your host's normal module installation flow. Bind the requirements shown by the plan:

• an authenticated host API router for account onboarding;
• private writable filesystem storage for isolated Codex OAuth caches;
• host environment storage for the secret-free pool configuration; and
• an HTTP service for the provider-profile editor asset.

In a compatible host, create a Codex Personal Pool provider profile from the Models screen, add the accounts you personally operate, and complete the official Codex login for each account. The host stores account aliases and relative cache paths in the profile; OAuth tokens remain in the private credential store.

The optional wolfy-j/codex-endpoint module adds a Codex CLI-compatible Responses endpoint and an operational dashboard. It is not required for native Wippy model use.

Security and intended use

This module is for one person operating their own installation, accounts, and clients. It is not a multi-user credential service or a way to share personal subscriptions. Confirm that your use complies with the applicable service terms and account rules.

Credentials, refresh tokens, prompts, generated text, and raw auth files are not exposed to the UI or usage APIs. Dashboard data is limited to redacted account aliases, allowance windows, aggregate token activity, traffic health, and safe request receipts.

Requirements

• A Wippy host with wippy/llm available.
• A private writable directory for each account's Codex auth cache.
• Owner-controlled Codex accounts authenticated through the official Codex login flow.

License

MIT. See LICENSE.