Traffic stays on localhost first.
Codex uses the OpenAI Responses API through one managed localhost proxy.
127.0.0.1:6767Small footprint. More headroom.
Your Codex workflow, with room to breathe. Optimize tokens, see your savings, and build your own stack of add-ons. All from one local app.
Enable Codex optimization, see route health at a glance, then pause, resume, or restart the local runtime.
Codex uses the OpenAI Responses API through one managed localhost proxy.
127.0.0.1:6767The app reads Headroom response metadata and stores aggregate activity locally. Request bodies and prompts are not persisted.
SQLite / app dataConfiguration writes are backed up, validated, and atomic. Failed startup restores native Codex routing.
backup → validate → replaceThe app installs its own Python 3.13 environment and Headroom proxy below the application-data directory.
headroom-ai[proxy]Browse a curated catalog—RTK, Codebase Memory, MarkItDown, and more—with impact scores, then tune skill add-ons at Lite, Full, or Ultra effort.
impact score · lite / full / ultraExport version details, sanitized logs, and redacted configuration. Database contents, prompts, and credentials are excluded.
local ZIP exportDetect Codex CLI, manage its reversible optimization route, and see every state from the desktop app.
Codex CLICompare original, optimized, and saved tokens with estimated input-cost savings, charted across today, 7 days, 14 days, or a month.
tokens + estimated USDBrowse local Codex activity by date range or model and inspect status, duration, and per-request saved cost without storing prompt content.
today / 7 days / 30 daysLaunch the desktop app at sign-in and keep it available from the system tray after closing the window.
sign-in · keep in trayCheck for updates from Settings and install signed releases with a single update-and-restart.
signed in-app updaterThe free plan tracks saved tokens per day against the 5M limit and tells you when optimization is bypassed until tomorrow.
5M saved tokens / dayInstall and control every add-on from the desktop app. Each one has a focused job in the Codex workflow.
Compresses command output before it spends context tokens.
Guides Codex toward leaner code without needless architecture.
Cuts response verbosity while keeping technical meaning.
Compacts context automatically as token use grows.
Keeps responses concise, evidence-first, and low-filler.
Navigates and edits code through symbol-level understanding.
Builds a persistent local knowledge graph of your codebase.
Brings current library documentation into Codex.
Converts PDF, Office, images, and audio into Markdown.
Keeps stable facts and project decisions across sessions.
Pairs a fast draft with security and logic review.
Optional by design. Install, enable, disable, or remove each add-on independently.
JIWWWWW manages the local optimization path around Codex. It does not replace Codex or its upstream provider.
Find Codex CLI and read its current provider configuration.
Enable Codex optimization. Its original provider configuration is backed up before routing changes.
Route compatible requests through the local Rust proxy and managed Headroom runtime.
Pause, quit, or recover from a failure by returning Codex to native routing.
Accounts and subscriptions are managed from the Account page in JIWWWWW. The public website does not collect payment details.
The Rust proxy does not persist prompt or request bodies. Requests still travel to the upstream provider configured for each enabled client through the local Headroom optimization runtime.
Yes. Pause or stop it from the desktop app. JIWWWWW removes its managed routing and restores the original client provider.
Auto start is optional in Settings. When enabled, the desktop app launches when you sign in, and closing the window keeps it available from the system tray.
Check for updates from Settings. JIWWWWW downloads signed releases in-app and installs them with a single update-and-restart.
Published installers are shown from the latest GitHub release. The current release feed determines what appears on the download page; unsupported or missing installers are never fabricated.
No. It runs beside Codex and manages a reversible local optimization route to the existing upstream provider.
Activity rows and daily aggregates are stored in SQLite inside the platform application-data directory.
The watchdog retries local services. After repeated startup failures, the app pauses optimization and restores native Codex routing.