/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Hands-on with seven coding agents tasked with building a website: Claude Code performed best, OpenAI's Codex lacked polish, and Replit failed to build the site

Timothy B. Lee / Understanding AI :

Understanding AI Timothy B. Lee

Context & Ripple Effects

The test arrives after coding agents moved beyond code completion toward end-to-end app creation: Replit had positioned its Agent as a tool that could build applications from prompts, while OpenAI introduced Codex CLI for terminal-based local tasks. A common website-building task makes the gap between those product promises easier to compare.

The result matters because it evaluates the finished work rather than only a model’s ability to generate snippets. Claude Code’s lead, Codex’s rougher output, and Replit’s failure show that agentic coding quality remains uneven across products aimed at similar outcomes.

First-order effects

  • Claude Code gains third-party evidence of stronger performance on this specific website-building task, while Codex’s output is characterized as less polished.
  • Replit’s failure to complete the site under this evaluation directly undercuts its positioning around prompt-to-app creation, at least for this test scenario.

Second-order effects

  • Teams comparing coding agents will have more reason to assess end-to-end completion and output quality, not just whether an agent can produce code or invoke tools.
  • OpenAI and Replit face pressure to improve the reliability and finishing quality of their agent workflows; Claude’s apparent advantage raises the competitive bar for comparable tasks.

Third-order effects

  • If repeatable evaluations keep producing divergent outcomes, coding-agent competition will be shaped less by feature checklists and more by dependable execution across multi-step software tasks.
  • The category may split between agents that assist inside established developer workflows and agents trusted to deliver a usable first version of an application; this single test does not establish which model will prevail.

The trend: Coding AI is shifting from autocomplete-style assistance toward competition over autonomous, end-to-end delivery of working software artifacts.

Discussion

  • @taumuyi Tau-Mu Yi on bluesky
    “The future of programming is English” #AI [embedded post]
  • @nic221 Nicole Hennig on bluesky
    What I learned trying seven coding agents - Timothy B. Lee https://www.understandingai.org/p/ what-i-learned-trying-seven-coding #AI #coding [image]
  • @binarybits Timothy B. Lee on x
    Today I wrote about trying out several coding agents. The “vibe coding” platforms did not work well but Claude Code and Cursor were quite good! [image]