100 Hours Testing Claude Code vs ChatGPT Codex (honest results)

Comments · 286

• NA

  @nateherk · 4 months ago (edited) · pinned

  FREE MONTH voice to text: <a href="https://get.glaido.com/nate">https://get.glaido.com/nate</a><br>All my FREE resources: <a href="https://www.skool.com/ai-automation-society/about?el=ClaudeCodeVsCodex&amp;hcategory=youtube-videos&amp;utm_campaign=free-group">https://www.skool.com/ai-automation-society/about?el=ClaudeCodeVsCodex&amp;hcategory=youtube-videos&amp;utm_campaign=free-group</a>

  9

• EM

  @emal8323 · 4 months ago

  This comparison was really helpful and honestly you put all the cards on the table! 💙

  2

• TH

  @thisisurplanet · 4 months ago (edited)

  I ran the stress test on writing serious academic research between Claude Code and Codex with the same experimental condition from scratch -- protocols, data, expected outcomes, and plus I gave them the access to my references resource vis Scopus API and NotebookLM. I would say it&apos;s Claude who wrote the most &apos;academic-paper-like&apos; and more rigorous, but consume hell amount of the token (on the 20 USD plan, Claude used 80% of 5h quota, Codex used 20% of 5h quota). What I guess so far is that Codex is really optimized for coding, not for writing. Because when it comes to coding session, in my use case of robotics and embedded systems, it&apos;s always Codex who finish the code properly and use the token efficiently.

  34

• PR

  @presto311 · 4 months ago

  A huge reason I switched to codex is the app integration as well as remote connections. Now I run all projects through another computer that&apos;s always on and can pickup projects on mobile too. I could never get dispatch to work very well on claude code.

  77

• CO

  @coolandnew9258 · 4 months ago

  Thanks Nate. I was having issues with claude code so this was super useful to know and I&apos;ve now converted my projects to codex

  2

• M4

  @M4ST3R_C0NTR0L · 4 months ago

  Claude Code in the terminal is my thinking space. Codex app is my execution space.<br><br>The terminal is where I plan, brainstorm, and work through ideas because all my existing workflows already live there.<br><br>The Codex app is what I use when I need action. It has browser use, computer use, and image creation, so it’s the tool I lean on when I want things done, not just talked through.

  3

• DA

  @darkpenink6730 · 4 months ago

  Thanks Nate! With all these technologies coming at you at such a speed watching your videos is helpful.<br>The way U explain and tell if use cases match with my requirements then I watch it in detail and adopt it else I can leave it.<br>main thing because of which I watch your videos is that you do not create a fear and click page but actually simply explain the concepts and leave the adoption part on the viewer. <br>I am grateful to you brother.

  1

• OF

  @OfftheRecordEconomics · 4 months ago

  Thanks for sharing!

  3

• IT

  @ITSupport-q1y · 4 months ago

  Awesome show thanks, would love to see what you thing of the new Gemini

  4

• SK

  @SkyrocketingTech · 4 months ago

  Great breakdown man

• GR

  @grumpycat9973 · 4 months ago

  Nate legend thx!!

  1

• CR

  @craftfuturism · 4 months ago

  Nate amazing job. Love the rapid fire breakdown. And yeah, as soon as you tell us about /goal then Claude has it... therein lies the challenge of these sorts of comparison videos. But still gtk. The browsing capabilities in @codex look helpful. More feedback: The one-shot prompt to dashboard evaluation is better than nothing but is so different than a plan + iteration (i.e. not trying to vibe code a prototype from a single prompt) approach, I am always unsure how much I can take away from it. The difference in cost etc is super helpful! Weird how one is so much different than the other wrt output tokens. Plan w/ claude, review+execute with codex... love that breakdown. More feedback: ngl, I thought AIS was Auto Insurance Specialists lol. But whatever. Subscribed.