@cjzafir: How Codex 5.5 medium is beating Codex 5.5 extra high? Add this rule in Agents. md: "Don’t fight errors! Whenever you en…

X AI KOLs Timeline News

Summary

A user shares a strategy for optimizing OpenAI Codex 5.5 by using the 'extra high' variant for planning and the 'medium' variant for execution with specific error-handling rules to improve efficiency.

How Codex 5.5 medium is beating Codex 5.5 extra high? Add this rule in Agents. md: "Don’t fight errors! Whenever you encounter the same error twice, research the web and find 3-5 possible ways to fix it. Then choose the most efficient solution and implement it." This prompt release stress to think hard and run into a loop of bad decisions but find new perspectives that actually worked. I ran this experiment on complex tasks (model training, running evals, converting best checkpoints to GGUF etc) and I encountered NO ERROR. Best part: minimal 5 hr and weekly limit usage. I am using Codex 5.5 medium (fast) and it feels instant. But here's the catch: Your session plan has to be designed by Codex 5.5 extra high! Use the medium variant, only to execute the plan. This way you're not using Codex 5.5 medium's loose thinking but using its fast speed to execute the task list properly. Try it yourself.
Original Article

Similar Articles

I let Codex and Claude Opus work on the same Java AI agent monolith

Reddit r/AI_Agents

A developer compares Codex 5.3 and Claude Opus 4.6 on autonomous Java AI agent development, finding that the model with more elegant architecture (Claude) often produced code that never executed, while the more boring and direct Codex improved the working product with practical fixes like timeouts and history recovery.