Codex
Thermal warnings the moment your game launches? Point Codex at the symptom and let it run xctrace
Tell Codex the concrete symptom, like a thermal warning on launch, and let it run xctrace, read the report, and fix the render path. One developer saw it route UIKit frames straight to Metal and add camera culling.
What changed
Thomas Ricouard (@Dimillian) reported Codex taking over his MacBook and iPhone Air to profile and optimize Dark Veil on its own. When he told Codex a thermal warning fired as soon as the game launched, Codex found UIKit frames were passing through instead of going straight to the Metal renderer, then added camera culling. In a follow-up he said Codex can run xctrace itself, build the report, and read it.
Primary source: https://x.com/Dimillian/status/2110672457879482622 Follow-ups: https://x.com/Dimillian/status/2110674553810927709 and https://x.com/Dimillian/status/2110688957679673684
Who is affected
People using Codex on Mac or iOS who are shipping games or other graphics-heavy apps and hit thermal or performance problems early in a run.
What to do now
- Name the concrete symptom (for example a thermal warning on launch), not a vague "make it faster."
- Ask Codex to run xctrace, produce the report, and read it.
- Let it chase the obvious render-path fix first before you stack FPS modes or deeper tuning.
What is not confirmed
This is a single field report from Dark Veil development, not an official Codex profiling guide. Results depend on your project, devices, and how much shell and device access you grant Codex. Not independently verified.
Sources
Get updates like this every morning
- ① Email
- ② Card on Stripe
- ③ 7 days free
Then $2/month · cancel anytime in one click