Small footprint. More headroom.

Less noise.
More room
to build.

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.

Local-firstManaged runtime on your machine
Codex-firstOptimization and add-ons in one app
SQLite ledgerActivity stays in local app data
Open source corePowered by Headroom AI
01 / CONTROL

One quiet layer between Codex and its provider.

Enable Codex optimization, see route health at a glance, then pause, resume, or restart the local runtime.

LOCAL PROXY

Traffic stays on localhost first.

Codex uses the OpenAI Responses API through one managed localhost proxy.

127.0.0.1:6767
TOKEN LEDGER

See optimization metadata.

The app reads Headroom response metadata and stores aggregate activity locally. Request bodies and prompts are not persisted.

SQLite / app data
SAFE RECOVERY

Designed to get out of the way.

Configuration writes are backed up, validated, and atomic. Failed startup restores native Codex routing.

backup → validate → replace
MANAGED RUNTIME

No system Python takeover.

The app installs its own Python 3.13 environment and Headroom proxy below the application-data directory.

headroom-ai[proxy]
Explore all the little details
ADD-ONS

Choose tools by expected value.

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 / ultra
DIAGNOSTICS

Inspectable without the sensitive bits.

Export version details, sanitized logs, and redacted configuration. Database contents, prompts, and credentials are excluded.

local ZIP export
CODEX CONTROL

One control plane for Codex.

Detect Codex CLI, manage its reversible optimization route, and see every state from the desktop app.

Codex CLI
SAVINGS DASHBOARD

Measure tokens and cost.

Compare original, optimized, and saved tokens with estimated input-cost savings, charted across today, 7 days, 14 days, or a month.

tokens + estimated USD
ACTIVITY EXPLORER

Trace every optimized request.

Browse 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 days
AUTO-START & TRAY

Starts when you do.

Launch the desktop app at sign-in and keep it available from the system tray after closing the window.

sign-in · keep in tray
IN-APP UPDATES

Stay current without reinstalling.

Check for updates from Settings and install signed releases with a single update-and-restart.

signed in-app updater
FREE PLAN GUARD

Know where you stand.

The free plan tracks saved tokens per day against the 5M limit and tells you when optimization is bypassed until tomorrow.

5M saved tokens / day
02 / ADD-ONS
11 AVAILABLE

Eleven add-ons. Switch on only what earns its place.

Install and control every add-on from the desktop app. Each one has a focused job in the Codex workflow.

01

Workflow & output

05
OUTPUT / 01

RTK

Compresses command output before it spends context tokens.

SKILL / 02

Ponytail

Guides Codex toward leaner code without needless architecture.

SKILL / 03

Caveman

Cuts response verbosity while keeping technical meaning.

CONTEXT / 04

Auto Compress

Compacts context automatically as token use grows.

POLICY / 05

Token Efficiency

Keeps responses concise, evidence-first, and low-filler.

02

Code intelligence

02
MCP / 06

Serena

Navigates and edits code through symbol-level understanding.

MEMORY / 07

Codebase Memory

Builds a persistent local knowledge graph of your codebase.

03

Knowledge & documents

03
DOCS / 08

Context7

Brings current library documentation into Codex.

MCP / 09

MarkItDown

Converts PDF, Office, images, and audio into Markdown.

SSOT / 10

Memory & SSOT

Keeps stable facts and project decisions across sessions.

04

Agent orchestration

01

Optional by design. Install, enable, disable, or remove each add-on independently.

03 / FLOW

Codex remains Codex.

JIWWWWW manages the local optimization path around Codex. It does not replace Codex or its upstream provider.

Detect

Find Codex CLI and read its current provider configuration.

Enable

Enable Codex optimization. Its original provider configuration is backed up before routing changes.

Optimize

Route compatible requests through the local Rust proxy and managed Headroom runtime.

Restore

Pause, quit, or recover from a failure by returning Codex to native routing.

Privacy boundary

Your prompt is not a product metric.

Read the privacy notes →
  • Local services bind to 127.0.0.1 by default.
  • Prompt and request bodies are not persisted by the Rust proxy.
  • Credentials and authorization headers are excluded from logs and diagnostics.
  • Activity and daily aggregates are stored in local SQLite.
04 / PRICING

Start free. Upgrade inside the app.

Accounts and subscriptions are managed from the Account page in JIWWWWW. The public website does not collect payment details.

Free

$0
  • 5M saved tokens per day
  • Local optimizer controls
  • Supported add-ons
Download
05 / FAQ

Before you route anything.

Does JIWWWWW upload my prompts?

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.

Can I turn optimization off?

Yes. Pause or stop it from the desktop app. JIWWWWW removes its managed routing and restores the original client provider.

Does JIWWWWW start with my system?

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.

How do updates work?

Check for updates from Settings. JIWWWWW downloads signed releases in-app and installs them with a single update-and-restart.

Which platforms are supported?

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.

Does it replace Codex?

No. It runs beside Codex and manages a reversible local optimization route to the existing upstream provider.

Where is activity data stored?

Activity rows and daily aggregates are stored in SQLite inside the platform application-data directory.

What happens if the local runtime fails?

The watchdog retries local services. After repeated startup failures, the app pauses optimization and restores native Codex routing.

Give your context more headroom.

Download JIWWWWW →