← X

🥇 Build track: Lazarus by Dean Sherry from Johannesburg, South Africa An agent

X · claudeai · July 17, 2026
Dean Sherry from Johannesburg created an agent called Lazarus that takes links to abandoned research code and automatically rebuilds it until it runs. The agent verifies whether the rebuilt code still reproduces the numerical results from the original research paper, and successfully identified and fixed a bug that had persisted in one program for 15 years.

Detailed Analysis

The "Built with Claude" hackathon, co-hosted with the Gladstone Institute and Cerebral Valley, produced a notable Build Track winner in Lazarus, an autonomous agent created by Dean Sherry of Johannesburg, South Africa. Lazarus is designed to take a link to abandoned or unmaintained research code and rebuild it from scratch, resolving dependency conflicts, environment mismatches, and other rot that accumulates when scientific software goes unmaintained. Crucially, it doesn't stop at getting the code to compile and run—it then verifies whether the reconstructed program still reproduces the original numerical results reported in the associated academic paper. The standout detail driving engagement is that Lazarus reportedly identified and fixed a bug that had persisted undetected in a piece of research software for 15 years, a claim that speaks directly to the reproducibility crisis that has plagued computational science for over a decade.

This kind of project matters because reproducibility failures are a well-documented, chronic problem in academic research. Studies across fields—from psychology to computational biology—have repeatedly found that a large fraction of published results cannot be independently reproduced, often because the original code depended on specific library versions, undocumented environment configurations, or institutional infrastructure that no longer exists. Manually resurrecting old codebases is tedious, unglamorous work that few researchers have time or incentive to do, which means broken or unreproducible research code often just sits abandoned indefinitely. An agent that can autonomously diagnose dependency rot, patch code, and cross-check outputs against a paper's published figures represents a meaningful automation of a task that has historically required significant human archaeology and domain expertise.

The broader significance ties into Anthropic's strategic push into life sciences and scientific research as a proving ground for Claude's agentic capabilities, evidenced by the hackathon partnership with the Gladstone Institute, a biomedical research organization. Commenters in the thread explicitly frame life sciences as a "wedge" for Claude's differentiation from more general-purpose chatbot applications, and the hackathon's framing around real scientific tooling (drug discovery pipelines, reproducibility agents) reflects Anthropic's broader positioning of Claude Code as infrastructure for scientific and engineering workflows rather than just conversational assistance. This fits a wider industry trend of AI labs seeking domain-specific, high-stakes use cases—science, coding, and research tooling—to demonstrate that agentic AI can perform sustained, verifiable, multi-step technical work rather than just producing plausible-sounding text.

The replies to the announcement, however, reveal significant friction points that complicate the celebratory narrative: users raise concerns about model routing and downgrades (being switched from higher-capability models to Opus without clear notice), usage-limit confusion, gift card and plan-tier grievances, and skepticism about whether hackathon outputs are genuinely novel tools or just another "chatbot wrapper." One reply raises a more philosophical concern about AI agents generating actions and toolchains faster than humans can audit them—a trajectory risk that becomes especially salient when agents like Lazarus are autonomously rewriting and validating scientific code with minimal human oversight at each step. This tension—between showcasing impressive agentic capabilities in high-value domains like scientific reproducibility while simultaneously fielding frustration over product reliability, transparency, and trust—is emblematic of where consumer-facing AI products currently sit: capable enough to solve decade-old bugs autonomously, yet still generating everyday friction around basic usage limits and model behavior that undermines confidence in the broader system.

Read original article →