Traffic stays on localhost first.
Codex uses OpenAI Responses and Claude Code uses Anthropic Messages through one managed proxy.
127.0.0.1:6767Local-first desktop optimizer
Save tokens.
Keep the workflow.
JIWWWWW routes Codex CLI and Claude Code through one managed Headroom AI runtime, with independent controls and safe recovery. Claude Code arrives in the next installer release.
Checking the latest GitHub release…
Local-firstManaged runtime on your machine
Codex + ClaudeIndependent, reversible routing
SQLite ledgerActivity stays in local app data
Open source corePowered by Headroom AI
01 / CONTROL
One quiet layer between your clients and providers.
Enable each detected client independently, see route health at a glance, then pause, resume, or restart the shared local runtime.
See optimization metadata.
The app reads Headroom response metadata and stores aggregate activity locally. Request bodies and prompts are not persisted.
SQLite / app dataDesigned to get out of the way.
Configuration writes are backed up, validated, and atomic. Failed startup restores native client routing.
backup → validate → replaceNo system Python takeover.
The app installs its own Python 3.13 environment and Headroom proxy below the application-data directory.
headroom-ai[proxy]Useful context, on demand.
Manage RTK, Codebase Memory, MarkItDown and other supported Codex add-ons without mixing their payloads into the app binary.
install / enable / disableInspectable without the sensitive bits.
Export version details, sanitized logs, and redacted configuration. Database contents, prompts, and credentials are excluded.
local ZIP exportOptimize either tool—or both.
Detect Codex and Claude Code, enable each route independently, and see both states from the desktop app.
Codex / Claude CodeMeasure tokens and cost.
Compare original, optimized, and saved tokens across today, 7 days, 14 days, or 30 days, with estimated input-cost savings.
tokens + estimated USDTrace every optimized request.
Browse local activity by date range, client, or model and inspect status and token counts without storing prompt content.
today / 7 days / 30 days
02 / FLOW
Your tools remain your tools.
JIWWWWW manages the local path around them. It does not replace Codex, Claude Code, or either upstream model provider.
Detect
Find supported clients and read their current provider configuration.
Enable
Choose Codex CLI, Claude Code, or both. Each selected client is backed up and routed independently.
Optimize
Route compatible requests through the local Rust proxy and managed Headroom runtime.
Restore
Pause, quit, or recover from a failure by returning clients to native routing.
- 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.
03 / 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
Pro
- Unlimited saved tokens
฿990฿490 billed yearly option- Billing portal in the desktop app
04 / 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.
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 or Claude Code?
No. It runs beside both clients and manages a reversible local optimization route to each 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 routing for every managed client.