Quick impressions: A week of using Codex more than Claude

Some speedy and very individual impressions from utilizing Codex much than Claude this week (I will do a afloat study during the play hopefully).

(1) While I tried this twelvemonth to support Claude and Codex connected par, having the aforesaid group of plugins/skills and truthful on, Claude had much skills, arsenic I created skills retired of immoderate sessions and not each of them were ported to Codex. Fix for this is simple: Point Codex astatine the Claude skills files and inquire it to toggle shape them for Claude

(2) When I was successful a unreserved (like debugging thing that felt urgent), I still opened Claude arsenic someway I felt much astatine location pinch it. I americium not saying it was better, but it was familiar, and erstwhile debugging, utilizing devices that I cognize is important.

(3) Changes created by Codex had less comments successful Ruby/Ruby connected Rails code. I liked that a lot, and I will soon stock immoderate experiments I ran connected this.

(4) The output of the Codex supplier harness is overmuch much “technical” than the 1 from Claude. Claude feels much for illustration your workfellow successful a Tuple convention penning to you while Codex feels much for illustration a type of Data from Star Trek.

(5) I want to unfastened galore much sessions of Codex and support them focused alternatively of a large convention of Claude arsenic I was doing before. This whitethorn not beryllium circumstantial to Codex, but I noticed it while moving pinch Codex.

(6) It feels to maine that Codex does changes faster than Claude. But aft making the main changes, it took a batch to decorativeness the propulsion request: rerunning galore tests, review, and truthful on. I for illustration the thoroughness of this, but successful the end, location was nary triumph successful position of clip difference.

(7) It felt to maine that Codex created a overmuch simpler solution successful position of codification architecture than Claude. Claude usually goes connected to create a batch of things: abstractions, concepts, Sorbet signatures, type aliases, and truthful on. Codex was a spot much contained and created less. This week I besides tested an improved travel of codification investigation -> creation alteration -> reappraisal alteration -> instrumentality -> verify. But I made some of them instrumentality the aforesaid request utilizing the aforesaid documents, and Claude’s codification was a spot much analyzable but handled cases.

(8) Codex besides made immoderate mistakes. Claude could understand my volition to branch retired from different activity and support them successful sync. Codex did immoderate nasty things for illustration branch A targets branch B that targets main, and erstwhile I asked it to rebase, it rebased pinch main, which created immoderate PR pinch 4000+ additions. I had to beryllium definitive and inquire it to rebase only pinch the target.

(9) For Codex, moving pinch Jira and Atlassian was a hassle successful my situation wherever I usage the CLI instrumentality and not the MCP. It opened JIRA to punctual maine to log in, past switched to the CLI, past backmost to the browser. In this case, Claude was overmuch much eager to effort to get what I want and to do it the measurement I want it done, based connected erstwhile sessions.

(10) Working pinch MCPs, I for illustration the Codex CLI attack more, wherever it asks maine to execute codex mcp login and each clip it opens the correct authentication and authorization flow. Claude sometimes tries to tally it automatically successful a turn, and it tin get stuck.

I deliberation the main quality I consciousness betwixt Claude and Codex is that Claude tries to spell supra and beyond what is asked and conjecture what you mightiness want and past straight do it, while Codex is much for illustration a companion that does what you show it but will not overdo it. It will extremity astatine the first motion that it mightiness beryllium done.