Key Takeaways
- Claude Code shines at design and greenfield work; pair with Codex for bug fixes.
- Use CLAUDE.md for guidance.
The Technique — What Developers Actually Use
A recent Hacker News thread asked developers which agentic coding tool they use: Claude Code, Codex, or something else. The responses reveal a clear pattern: most experienced devs aren't picking one tool — they're using both.
One developer reported: "So far been quite productive for some greenfield rewrites and refactors of existing code. Though bug fixing our main project it's more hit and miss, though Codex GPT 5.5 High can be very good at spotting subtle issues."
Another echoed: "I find claude to be significantly lazier or require significantly more guidance. it does, however, have better design and ui/ux intuition."
Why It Works — The Strengths of Each Tool
Claude Code's Superpowers
- Greenfield projects: Claude Code excels at starting from scratch — building new architectures, designing UIs, and creating cohesive codebases.
- UI/UX intuition: Multiple users noted Claude Code has better design sense. When you need a frontend that looks good, Claude Code is the pick.
- Refactoring: It handles large-scale code restructuring well, understanding how components connect.
Codex's Superpowers
- Bug fixing: Codex (especially GPT 5.5 High) is better at finding subtle issues in existing code.
- Detailed planning: One developer uses Codex 5.5/4.8 for creating "very detailed plans" before implementation.
- Subtask delegation: Some devs use Codex for easy features and reserve Claude for larger, harder tasks.
How To Apply It — A Practical Workflow
Use Claude Code for architecture and design
- Create CLAUDE.md with your project's design principles, tech stack, and conventions.
- Start new features with:
claude code --task "Design and implement a new user dashboard"
Use Codex for bug fixing
- When you hit a subtle bug, switch to Codex with:
codex --task "Find why this API returns 500 on empty input" - The community reports Codex is more reliable for edge-case hunting.
- When you hit a subtle bug, switch to Codex with:
Combine in a pipeline
- Use Codex for initial planning (detailed specs).
- Use Claude Code for implementation (better design intuition).
- Use Codex for code review and bug detection.
Security considerations
- One developer noted: "Security is a thing here now so sec guys feel more comfortable with big names rather than 'random' open source." If your org has security requirements, stick with Claude Code and Codex — they're the established players.
The Takeaway
Don't be dogmatic. Claude Code and Codex have different strengths. Use Claude Code for the big picture — architecture, design, refactoring — and Codex for the fine details — bug fixing, edge cases, implementation of straightforward features. Your CLAUDE.md should reflect this hybrid approach by specifying what you want Claude Code to focus on.
Source: news.ycombinator.com
