Select the task mode
Implementation context, diff review, architecture mapping, or focused test selection.
Local plugin for Codex CLI
Give Codex the right files. Before it searches the repo.
Codex Speeder maps the relevant files, callers, risks, and tests before Codex starts broad repository discovery. In our controlled benchmark, it used 34% fewer input tokens and completed the task 19% faster—with equal quality results.
Runs locally No source uploads macOS, Windows & Linux
codex — review
› Review the rejected RPC handling
Speeder Mapping repository…
EVIDENCE MAP3 relevant files identified.
- 01 implementation symbol
- 02 direct callers & risk boundary
- 03 focused regression test
↳ Codex Speeder: narrowed this task to 3 relevant files and 1 focused test
01 / Mechanism
A bounded starting point, built from repository evidence.
Speeder does not replace Codex. It prepares a focused evidence map; Codex performs the implementation, review, or analysis with less broad discovery.
Trace direct evidence
Resolve symbols, callers, configuration, tests, and risk boundaries without reading the repository broadly.
Return a compact map
Codex receives the evidence packet, continues the normal task, and reuses unchanged results when possible.
02 / Benchmark
Measured on a cross-file TypeScript task.
A controlled, paired end-to-end Codex CLI comparison on a 553-file repository. Each condition used the same prompt, source snapshot, task, permissions, and quality criteria.
fewer input tokens
153,323 → 100,599 average
faster completion
50.8s → 41.1s average
fewer tool calls
20 → 14 average
quality checks passed
Equal to Codex alone
Cold isolated comparison using Codex CLI 0.146.1, GPT-5.6 Terra, medium reasoning. This is a scoped cross-file navigation result—not a universal speed or cost guarantee.
Read the full methodologyKeep the normal Codex workflow. Start with better context.One-time individual license for Python and TypeScript repositories.
Get Codex Speeder — $19 S
Repository analysis
Runs on your machine03 / Data handling
Repository analysis runs locally.
Speeder reads the Git repository you point it at and writes a local content-hash cache. The analysis engine does not contact a network provider or send repository content to the publisher.
- No publisher telemetry
- No hosted code index
- No separate Speeder account
Individual license
One-time license. No subscription.
Best suited to unfamiliar paths, cross-file changes, code review, and architecture work in Python or TypeScript repositories. Trivial known-file edits bypass structural discovery.
How delivery works
- 1Pay securely with Stripe
- 2Receive a private GitHub repository invitation
- 3Follow the included setup guide in Codex CLI
Individual license
$19USD · one time
- Private GitHub access and setup guide
- Local analysis engine and Codex skill
- macOS, Windows & Linux binaries
- Python & TypeScript repositories
- Updates for this major version
Secure Stripe checkout · GitHub username required for delivery
Access normally arrives within minutes. Need help? Contact support.
04 / Details
Technical and licensing questions.
What do I need before buying?+
You need a GitHub account for private repository delivery, plus Codex CLI and Git. Speeder supports Python and TypeScript Git repositories on macOS, Linux, and Windows.
How do I receive the plugin?+
Checkout collects your GitHub username without the @ symbol. After payment, we invite that account to the private plugin repository, where the setup and update instructions are available.
How quickly is access delivered?+
Automated GitHub delivery starts after Stripe confirms payment and normally completes within a few minutes. If access does not arrive within 15 minutes, contact support with your purchase email and GitHub username.
What problem does Speeder solve?+
It reduces broad repository discovery before implementation, review, architecture analysis, and test selection. Speeder traces the direct evidence for a task and gives that map to Codex as a starting point.
Is this just a set of prompt instructions?+
No. The plugin includes a local analysis engine and platform binaries. The skill routes Codex into the appropriate mode; the engine performs deterministic repository analysis and returns a compact evidence packet.
Is Codex Speeder a token compressor?+
No. It does not rewrite or compress source code. It identifies relevant files, direct callers, configuration, risk boundaries, and focused tests so Codex can avoid unnecessary discovery.
Does my source code leave my machine?+
Speeder runs locally in Codex CLI. Its repository analysis does not contact a network provider or send your source code to the publisher.
Which projects are supported?+
Python and TypeScript Git repositories on macOS, Linux, and Windows. TypeScript analysis requires Node.js; Python analysis requires ripgrep.
When should Speeder not run?+
A trivial edit with an exact file and validation already known does not need structural discovery. Speeder is designed to reuse the known file list instead of adding another repository scan.
Will every task be 19% faster?+
No. The published result is a scoped benchmark for one cross-file TypeScript navigation task. It demonstrates that Speeder can reduce discovery work under those conditions; it is not a universal speed, token, or cost guarantee.
For tasks where repository navigation is part of the work