Jan 28, 2025 · 34m · latent-space
Beating OpenAI and Anthropic by Looking At Data: the new #1 on SWE-Bench w/ W&B CTO Shawn Lewis
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Weights & Biases CTO Shawn Lewis joins the Latent Space Podcast to detail how he achieved a record 64.6% solve rate on the SWE-bench Verified leaderboard using OpenAI's o1 model, the Phase Shift framework, and deep observability tooling built on Weave.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
speaking balance: gold is the hosts, purple is the guest (3 minute bins)
Shawn firmly rejects the dismissive claim that his result is trivial brute forcing, explaining that every top lab uses parallel rollouts and that gaining 6% at the top of the benchmark is exponentially difficult.
Hardest push from the hosts ▶ 15:52 Swix challenges pure o1 architecture with Aider benchmarkSwix challenges Shawn's reliance on pure o1 by citing Paul Gauthier's proven Aider setup combining o1 as an architect with Sonnet as a code generator.
Biggest teaching moment ▶ 18:22 Quantifying instance difficulty from public leaderboard solvesShawn teaches the hosts a clever evaluation technique: calculating an empirical difficulty score for benchmark instances by aggregating total public solves across leaderboard submissions.
The host holds their own ▶ 15:52 Host introduces competitor metagame dynamicsSwix demonstrates deep industry awareness of agent architectures by bringing up specific multi-model configurations on competing coding benchmarks to test Shawn's architectural choices.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The hosts as informed peer | Guest teaching | Guest disagreement | The hosts pushing back | Why |
|---|---|---|---|---|---|---|
| The Philosophy of Dogfooding and AI Tool Evolution | 3 | 2 | 0 | 0 | Swix introduces Shawn and sets up a conversational inquiry about why Weights & Biases ventured into SWE-bench agent tooling. Shawn provides an expansive backstory detailing his history with gaze tracking, experiment tracking, and the dogfooding philosophy behind Weave. | |
| Transitioning from Model Evals to Coding Agent Frameworks | 5 | 2 | 1 | 2 | Alessio references their past interview with Anthropic regarding SWE-agent evals, prompting Shawn to share his setup. Swix gently intervenes to redirect Shawn from getting too deep into the weeds before establishing the headline results. | |
| Visualizing Agent Runs and Bottlenecks with Eval Studio | 3 | 5 | 0 | 1 | Shawn screen-shares Eval Studio and walks through tracking metrics across SWE-bench runs, explaining kinks in reasoning token distributions. The hosts listen as Shawn illustrates the evolution from Google Sheets to integrated Weave evals. | |
| Leveraging OpenAI o1 for End-to-End Agent Logic | 6 | 5 | 4 | 5 | Alessio prompts a technical breakdown of Shawn's o1-driven agent architecture. Swix pushes back by citing Paul Gauthier's findings on Aider using o1 as architect and Claude Sonnet as coder, leading Shawn to counter why he found o1 agentic reasoning uniquely challenging and effective. | |
| Data-Driven Debugging and Linear Agent Traces | 4 | 6 | 0 | 1 | Shawn explains how aggregating public SWE-bench solve counts yielded per-instance difficulty scores to pinpoint prompt regressions. He demos the linear step-by-step trace viewer and argues that manual inspection of agent data remains essential. | |
| Configuration Diffing and Framework Tracking in Weave | 6 | 5 | 0 | 2 | Alessio asks an incisive diagnostic question regarding how to differentiate prompt regressions from tool description failures. Shawn walks through Phase Shift's configuration diffing and code tracking inside Weave to identify prompt phrasing deltas. | |
| Phase Shift Roadmap and AI-Assisted Tool Development | 5 | 4 | 0 | 1 | Alessio asks whether Phase Shift can be polished by its own agent and used for real-world tasks beyond benchmarks. Shawn explains that the UI was actually built with Cursor and notes the framework is currently tuned specifically for SWE-bench verified. | |
| SWE-Bench Trajectories and the Cross-Check Selection Mechanism | 6 | 6 | 4 | 4 | Swix brings up critique from competitor agent builders who dismiss Shawn's score as expensive rejection sampling. Shawn defends the validity and necessity of parallel rollouts and cross-check selection, noting every top leaderboard participant relies on trajectory filtering at this frontier. |