1. Use Codex for judgment
Let Codex inspect the repo, decide whether the task is safe, and choose the smallest allowed file list.
Codex cost guide
How to reduce Codex cost without leaving Codex.
The goal is not to replace Codex. The goal is to stop spending expensive reasoning tokens on every repetitive implementation loop. tokenpatch lets Codex keep planning and judgment while a lower-cost executor writes the bounded patch.
2. Run tokenpatch for execution
Use tp: or the tokenpatch CLI fallback for tasks like tests, copy changes, route wiring, and small bug fixes.
3. Measure the applied patch
Compare the all-strong baseline with executor cost and review the savings ratio in the tokenpatch report.
| Codex workflow | Cost risk | tokenpatch mitigation |
|---|---|---|
| Repeated test-writing loops | High implementation token spend | Run bounded executor tasks against known test files. |
| Small UI edits | Strong model spends tokens on low-risk patch text | Use allowed files and acceptance criteria before execution. |
| Final review | Quality risk if skipped | Keep Codex and the developer in the review loop. |