Claude Is Back. I Still Reach for Codex.
The speaker explains their preference for using Codex over Claude, citing superior tooling, a better desktop application, and specific strengths in front-end design and SVG work. Despite Claude's return, they continue to reach for Codex for their development needs.
Summary
The speaker discusses their ongoing preference for Codex as a development tool, even though Claude has become available again. They outline multiple reasons for this preference: they appreciate Codex's tools and desktop application more than alternatives, and they prefer using it on a computer. The speaker notes that Codex's Opus 551 model is not annoying to use. Additionally, they highlight Codex's capability in handling long-term agent tasks effectively. They emphasize that Codex offers a favorable cost-to-performance ratio and is notably fast. Most importantly, the speaker identifies Codex as exceptional for front-end design work, particularly in working with SVG and visual display work, which they express strong enthusiasm for.
Key Insights
- The speaker prefers Codex's tools and desktop application over alternatives, and finds the computer-based workflow more suitable for their needs
- Opus 551 is characterized as not annoying to use, suggesting a positive user experience compared to other options
- Codex handles long-term agent tasks effectively, indicating capability in sustained, complex workflows
- Codex offers a combination of speed and cost-effectiveness that the speaker values highly
- Codex is exceptional specifically at front-end design and SVG work, making it the preferred choice for visual and display-oriented development
Topics
Transcript
[0:00] I brought it back to myself, at least. So, Clawd is back at the dock. I will say that I still reach for the Codex. Why am I reaching for the Codex? I like their tools better . I like the desktop app better. I prefer using a computer. I just like it better . Um, Opus 551, it's not annoying. Secondly, he copes well with long-term agent tasks. Third, it's fast and cheaper, so we love it. Fourth, it is exceptional in [0:30] front-end design. It is exceptional at working with SVG. You should use it for visual frontend, a kind of display work. I really like it. Ahem.
Full transcript available for MurmurCast members
Sign Up to AccessMore from How I AI
Warp agents open PRs to fix the factory itself
Programming agents can autonomously improve factory systems by analyzing failed launches and proposing specific updates to agent definitions. A self-improvement loop enables observer agents to detect failures and generate evidence-based modifications that prevent recurring issues, such as changing specific steps in factory agent procedures.
Humans are still the bottleneck in Warp’s AI factory
Warp discusses how human code review has become the main bottleneck in their AI-assisted software development process, with a 3.5-hour delay from PR to first human review compared to 35 minutes from launch to PR. They're evolving their workflow to reduce human dependency by allowing requesters to review agent-generated code themselves, and plan to eventually skip review entirely for low-risk tasks by treating code review as a risk management exercise.
I Quit Claude Because It Was Annoying
The speaker explains why they stopped using Claude, citing frustrations with its tendency to produce nonsensical output and communicate in an unnatural, non-human manner. They mention considering a switch to Opus 5.5 but remain uncertain about fully migrating their work tasks.
Claude Is Not a Party Boy
A humorous character description of Claude as someone with traditional values who prioritizes work over social indulgence. The transcript portrays Claude as principled, occasionally frustrating, and willing to push back on tasks he finds objectionable.
My AI SVG Prediction Was Wrong
The speaker's prediction that Anthropic would excel at SVG creation proved incorrect. Instead, Astra and Soul demonstrated superior performance in creating SVG characters and cute illustrations.