physicsblog
Siddharth Mishra-Sharma
More in physical sciences and engineering
- Using physics tools to study a forestphysics, 1 Oct 2026
- Ke Xiao, Han Li, Teng Zhang, Yangchen Xu, Runze Mao, Zhi X. Chenengineering, 15 Jul 2026
- Matthew Schwartzphysics, 23 Mar 2026
- Zeke Hausfatherclimate science, 24 Feb 2026
- Benjamin J. Shieldschemistry, 19 Feb 2026
What they did
Mishra-Sharma describes setting a Claude Code agent to build a differentiable cosmological Boltzmann solver (CMB physics) over several days, in a task outside his core domain. The setup used a root instruction file with the plan, a changelog as persistent memory (including failed approaches and why), git commits after each meaningful step, and unit tests against the CLASS C code as the oracle. He states that tasks suited to this mode are well-scoped with clear success criteria, and that a coupled pipeline like a Boltzmann solver suits a single sequential agent spawning subagents rather than a swarm.
In their words
"long-running autonomous scientific work today crucially depends on the agent having a way to know whether it’s making progress."
"The failed approaches are important—without them, successive sessions will re-attempt the same dead ends."
"Notably, the task isn’t in my core scientific domain"
Lessons they draw
- Give the agent a test oracle: a reference implementation, a quantifiable objective or an existing test suite (Mishra-Sharma).
- Keep a progress file that records failed approaches and why, so later sessions do not repeat them (Mishra-Sharma).
- Use git commits as coordination: commit and push after every meaningful unit of work for a recoverable history (Mishra-Sharma).
- Choose well-scoped tasks with clear success criteria for hands-off work (Mishra-Sharma).
Limits of this account
Author is employed by the vendor and the post is hosted on its site; it is a workflow how-to built on one worked example.