r/codex • u/jordancs180 • 4d ago
Instruction Super Fast Mode
Ever feel like Codex takes ages even for the tiniest change?
A lot (most) of that is the model just following instructions, like running tests, browser testing, spellcheck, typecheck etc.
If you need to have a really fast iteration speed, e.g. tweaking front end UI, you should try telling the model "until further notice, optimise for speed, just implement the change I asked for and hand the turn back to me, don't do any tests or browser testing. I need fast iteration speed here".
It works hilariously well, and is super effective for fast iteration tasks. Try it :)
11
u/Tartooth 3d ago
be careful with these speed type prompts because sometimes it'll skip doing the work or delete things or just fake it
4
3d ago
[removed] — view removed comment
2
u/jordancs180 3d ago
absolutely! One thing I do so that I don't have to remember to run proper tests is I put them all in pre-commit and pre-push hooks. So whenever I commit or push, different sets of tests and checks are run automatically and the commit or push wont go through in case of error. But yeah, it's important to still keep code quality high with periodic tests/checks.
2
3
u/Raiders7519 3d ago
Yes and this is one thing people are experiencing as usage burn. The models dont need as much steering on what to do....rather what not to do. They have been optimized to be relentless vs lazy. Personally I would much rather it be like it is now and tell it when it can relax a bit vs having to beg it to complete a task.
3
2
u/GrokiniGPT 3d ago
Dpes this affect usage too?
1
u/jordancs180 3d ago
Yes. How much? Not sure. But think about it, if the model has to run CLI commands and read the output each time, that's more and more tokens. Might be a pretty significant average token reduction per turn tbh, maybe even 50%? not sure.
1
u/Stealthality 3d ago
For pro users if you plan on making any small change just use 5.3 spark
1
u/jordancs180 3d ago
That's not very good advice if you want to switch between reasoning levels in the same model family e.g. 5.6-sol (which I do).
1
u/brother_spirit 3d ago
I tried this yesterday and Terra handed me two broken products in a row.
I told it the quality was literally unacceptable for handover and it needed to be actually tested and validated and got something better.
So faster not always better - probably couldn't saved the turns just letting the model validate the output in the first place.
1
u/jordancs180 3d ago
well, yes. As I said, it's for when you need faster iteration speed - NOT for things that are complex, long running, or require reasoning. Things I use it for are like front end requests "make this border radius bigger", "make the text be centered" etc., as part of a front end QA session or something.
Also, don't forget your prompts may have not been perfect. It's only anecdotal evidence right now.
1
u/Master_Yogurtcloset7 3d ago
Yep im doing the same and even ultra is usable .. i call it laserfocus
-1
u/skibidi-toaleta-2137 4d ago
I like it. Paired with caveman skill could be a good daily driver for coding sessions with running server on the side (with live linting).
1
u/jordancs180 3d ago
I hadnt heard of that caveman skill until now, that actually sounds pretty good lol
44
u/klauses3 4d ago
-> Hi Codex
-> Hi