Agentic Science Worker

Autonomous AI infrastructure for computational materials research

Status
Past
Period
2026
Role
Creator
Thread
Self-driving labs

Most discoveries die between the lab and the real world. But there’s an earlier bottleneck. Before you can translate a discovery, you have to make it. And the rate of discovery in computational materials science is throttled not by compute, not by theory, but by the human overhead of running the loop.

Find the paper, extract the parameters, configure the simulation, submit the job, wait, parse the output, check it against what’s known, decide what to run next. Each step is trivial. Together, they determine how many questions actually get asked.

Agentic Science Worker was my attempt to remove that overhead. Built on Claude Code, it operated as an autonomous computational scientist that handled the full execution loop while the researcher stayed in control of direction.

It ran molecular dynamics in LAMMPS with parameters taken from the literature, and density functional theory calculations in Quantum ESPRESSO. It queried materials databases, extracted information from the literature, submitted and orchestrated HPC jobs, and validated results against published benchmarks.

The system didn’t guess. It validated against published results. It documented its reasoning. It maintained scientific standards while removing the friction that makes those standards expensive to uphold.

I built an 11-tier benchmark framework to evaluate it, from single-tool tasks through frontier HPC+ML hybrid workflows. Full logging, full reproducibility. If it couldn’t be verified, it didn’t count.

This project applied the same thesis I hold for materials. Work dies from friction, not from being wrong. The value is in removing that friction, whether between lab and deployment or between question and answer.

github.com/fl-sean03/agentic-science-worker