🧠 Context Control Panel for Codex
Make Codex's context visible, locatable, and precisely manageable — like memory.
Features · Architecture · Install · FAQ
This project lets you see Codex's context consumption, what's retained after compression, and edit it yourself. It also lets you replace Codex's system prompt to break through Codex's limitations, and replace Codex's compression prompt for better compressed output.
View Codex's context by role, check token usage per turn, and see when prompts are injected.
Chat with a dedicated secondary model to analyze, edit, compress, and manage the main Codex's context. You can plug in a cheap secondary model.
View token consumption, cache hit rate, and estimated cost across your Codex session.
Replace Codex's system prompt and native compression prompt for jailbreaking and better compression quality.
No Codex source code changes, no official tools replaced. Sits in the middle as a local proxy, compatible with all native features.
flowchart LR
CD["Codex CLI / Desktop"]
PX["Responses Proxy\n:8787"]
WEB["Web Backend\n:8765"]
FE["React Workbench"]
OAI["OpenAI API / Upstream Model"]
CD -- "POST /v1/responses" --> PX
PX -- "Rebuilt request" --> OAI
OAI -- "SSE stream" --> PX
PX -- "SSE stream" --> CD
FE -- "HTTP edit/settings" --> WEB
WEB -- "HTTP proxy control" --> PX
PX -. "WebSocket realtime events" .-> FE
How It Works:
Every Codex request follows the same path — there is no "pass-through if unedited" branch:
flowchart LR
A["Codex sends request"] --> B["cursor diff"] --> C["Update transcript"] --> D["Rebuild input"] --> E["Forward upstream"]
- Transcript is the single source of truth: what users see in the workbench, edit, and what ultimately gets sent upstream
- Without edits, the rebuilt input is naturally equivalent to the original Codex input
- With edits, upstream receives the edited transcript + new content from the current turn
- During compression, Codex's native compression prompt is replaced with a custom version, and the result is written back to the transcript
1. Install
Download and run the latest Windows installer from Releases.
2. Enable CLI Proxy
codex ctx proxy on # Enable proxy
codex # Use Codex normally
codex ctx proxy status # Check status
codex ctx proxy off # Disable proxy3. Desktop Support
codex ctx desktop on # Enable Desktop mode
codex ctx desktop status # Check status
codex ctx desktop off # DisableNote
Desktop mode modifies local Codex provider configuration. CLI mode only adds a shim and does not affect any config files.
# Install dependencies
npm install
npm run setup:python
# Run the full local flow
npm run codex
# Run only the context window
npm run window
# Run checks
npm run typecheck
npm test
# Build Windows installer
npm run package:winIs this a Codex plugin?
No. Codex Context Studio is a local context layer around Codex, implemented through proxy technology.
Will it break the cache?
Compression is not a frequent event. After compression, it only recalculates once, which is more cost-efficient than carrying useless context. In practice, cache hit rate only drops by 5–10%.
Why not just rely on auto-compaction?
Compatible with native compression. The project also helps replace compression prompts — we've built more precise, targeted compression features.
Who is this for?
People who want better control over context, have their own ideas about compression, or want to modify Codex's prompts.
GPL-3.0 · Made with ❤️ for Codex power users



