# Siddharth Mishra-Sharma

- Researcher: Siddharth Mishra-Sharma
- Role: Researcher on Anthropic's Discovery team (as stated)
- Field: physics
- Tools: Claude Code (Opus 4.6); tmux on an HPC cluster with SLURM; JAX; CLASS (reference implementation)
- Published: 2026-03-23
- Source: https://www.anthropic.com/research/long-running-claude
- Latest flagship models when written: Claude Opus 4.6 and GPT-5.4. Latest now: Claude Opus 5.5 and GPT-6.1 Sol.

## 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.
