๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Vox
@Voxyz_ai
Obsessed with getting AI to do real work. Practicing the AI-native future before it arrives. Builds, model tests, prompts to copy.
๊ฐ€์ž… November 2025
207 ํŒ”๋กœ์ž‰ ์ค‘    20.6K ํŒฌ
Codex has now passed ๐Ÿญ๐Ÿฑ ๐—บ๐—ถ๐—น๐—น๐—ถ๐—ผ๐—ป users and grown ๐Ÿฎ.๐Ÿฑ๐˜… over the past month. That pace is clearly taking market share from Claude Code. I still use both Claude Code and Codex heavily. On model quality alone, Opus and Sol are very hard to separate. Overall, Iโ€™d call it roughly even. Day to day, though, Iโ€™m almost entirely in Codex. I mostly use Claude inside Herdr fleets, where it joins the other agents for something closer to an internal team discussion. ๐Ÿญ. ๐—–๐—ผ๐—ฑ๐—ฒ๐˜… ๐—ถ๐˜€ ๐˜๐—ต๐—ฒ ๐—ฎ๐—ฝ๐—ฝ ๐—œ ๐—ผ๐—ฝ๐—ฒ๐—ป ๐—ฒ๐˜ƒ๐—ฒ๐—ฟ๐˜† ๐—ฑ๐—ฎ๐˜† The Codex App is just smooth. I can queue prompts, sessions are easy to find, and switching between them never gets in the way. Computer use and browser use are much more reliable. Claude still fails midway through a run pretty often. Codex even notices whether the cursor is visible enough to use. For browser work, I recently started preferring ego-browser (ego-lite). Worth trying. I worried about Codexโ€™s smaller context window. After multiple compactions, it still remembers what we were doing. Claude sometimes compacts and feels like an entirely different person. I also have Codex clean up my agent skills from time to time. First it inventories them without touching any files: every skill goes under KEEP or REMOVE, with a one-sentence reason. I read the list, then Codex deletes only the REMOVE items I approve. Duplicates, stale skills, and irrelevant ones surface fast. /goal is useful too. The session knows when to pause, and the goal stays visible in the App. I donโ€™t have to explain it again. ๐Ÿฎ. ๐—ช๐—ต๐—ฒ๐—ฟ๐—ฒ ๐—–๐—น๐—ฎ๐˜‚๐—ฑ๐—ฒ ๐˜€๐˜๐—ถ๐—น๐—น ๐˜„๐—ถ๐—ป๐˜€ Fable is still very wise. Claudeโ€™s hooks go deeper. When I want fine-grained control over how a session behaves, there are still plenty of details Codex canโ€™t touch. Routines and Managed Agents are more mature too. The Team plan also offers Premium Seats, which makes Claude easier to run across a team. ๐Ÿฏ. ๐—ง๐—ต๐—ฟ๐—ฒ๐—ฒ ๐—บ๐—ผ๐—ฟ๐—ฒ ๐—ฟ๐—ฒ๐—ฎ๐˜€๐—ผ๐—ป๐˜€ ๐—œ ๐˜‚๐˜€๐—ฒ ๐—–๐—ผ๐—ฑ๐—ฒ๐˜… Image generation saves me a ridiculous amount of time. Claude has barely touched this. Geminiโ€™s Nano Banana Pro used to be my favorite, and for a while I thought it was the best. Codex image generation replaced it in my workflow. Nano Banana Proโ€™s output isnโ€™t as good as GPT Image 2, and Gemini is still terrible at coding. Iโ€™ve also been testing subagent setups a lot lately. I made Luna Max my default subagent, then removed it a few days later. Itโ€™s fast, but open-ended development creates enough rework to erase the time it saves. I now default to Sol Medium. Hard tasks go to Sol High. For small tasks with clear boundaries and easy checks, I still use Luna. Haiku often isnโ€™t usable on the same work. I tested several models on one very specific step. Before image generation, a system prompt has to interpret the userโ€™s instruction and write the processing prompt that comes next. Luna kept beating Sonnet 5 and Gemini Flash 3.7. It was faster and more reliable across repeated tests. Sonnet 5 costs more. Weird result, but I kept getting it. Codex App Server also fits how I work. The spec is open, itโ€™s easy to hack on, and there arenโ€™t many restrictions. If I could keep only one today, Iโ€™d keep Codex. For real projects, I still keep both open. Claude and Codex get one pane each. One builds, one reviews, and the main agent sits in the middle assigning work, waiting for results, and following up. I used to handle every handoff myself.
๋” ๋ณด๊ธฐ