Best fit
Small and medium coding tasks with clear allowed files, such as UI copy changes, tests, route wiring, simple bug fixes, and bounded refactors.
Codex use case
Save Codex tokens without leaving Codex.
Codex is strongest when it owns planning, repo understanding, and review. tokenpatch adds a lower-cost execution lane for narrow changes, so the expensive model does not need to spend every implementation token.
How it works
Ask Codex normally, add tp: when the task can be bounded, and tokenpatch applies a checked patch locally.
What you see
Reports show executor tokens, estimated all-strong baseline, actual cost, savings ratio, and cost per applied patch.
Example prompt
tp: add billing edge-case tests. Only modify tests/billing.test.ts.
Codex still decides whether this is a safe bounded task. tokenpatch then creates a checkpoint and runs the executor.
Why Codex users care
Long implementation loops can consume high-value reasoning tokens. tokenpatch moves the repetitive patch-writing step to the executor lane.
Recommended workflow
Use Codex for exploration, ask for a narrow allowed-file list, run tokenpatch, then let Codex review the generated diff and tests.
| Codex task type | Use tokenpatch? | Reason |
|---|---|---|
| Single-file test addition | Good fit | Clear boundary, easy validation, measurable executor cost. |
| Cross-repo architecture migration | Keep in Codex | Requires broad judgment and repeated human review. |
| Small UI copy or route wiring | Good fit | Allowed files can be named before execution starts. |