Vol. 1 · Edition 027Free · No paywall

Everyone Needs a Samwise

AI news · Synthesized · Opinionated · 🌿

60+
curated scientific skills
genomics · proteomics · structural biology · cheminformatics
Tools & Infra
By Sam Taylor with Samwise

On what Claude Science actually does differently, the reviewer agent that checks your citations, and what the AI for Science grant program is selecting for

Anthropic built Claude Code for the lab. The reviewer agent is the part worth watching.

Source lean on this story
▲ avg

Anti-AI

00

Skeptic

01

Neutral

00

Pro (practical)

02

Pro (hyped)

01

← Anti-AI · Pro-AI →

Last year Anthropic shipped Claude Code, and software engineers got a development environment where the model was so tightly integrated into the edit-run-debug loop that context-switching between the AI and the terminal mostly stopped being a thing. The pattern was deliberate: find the most painful friction in an expert workflow and collapse it.

Claude Science, which launched in beta on July 1, is the same pattern applied to scientific research.

Desktop app. Runs Python, R, and shell. Connects to your HPC cluster over SSH, or Modal for on-demand compute at scale. Sixty-plus curated skills and connectors pre-configured for genomics, single-cell analysis, proteomics, structural biology, and cheminformatics. Every output carries an auditable history of how it was produced, so a collaborator or peer reviewer can trace the path from raw data to published figure.

Multiple outlets reached for the same phrase: "Claude Code for scientists." That's the positioning and it's accurate.

What the reviewer agent actually does

Here's the part that's different from just Claude running Jupyter notebooks.

Claude Science includes a reviewer agent that runs after analysis is complete. It checks citations against the literature, flags numbers that don't appear in the cited sources, and identifies figures whose visual output doesn't match the code that generated them. When it finds a mismatch, it self-corrects.

That's a meaningful design choice, not a convenience feature. The reproducibility crisis in academic research is mostly a citations-and-methodology problem. Bad papers fail because figures get visually edited after generation, citations get misread six months after the researcher read them, and statistical procedures aren't clearly connected to their inputs. A reviewer agent that runs those checks automatically is attacking the actual failure mode.

$30k
Maximum in Claude API credits per AI for Science grant project

→ Source: Anthropic

The grant program: Anthropic is funding up to 50 Claude Science AI for Science projects with up to $30,000 in Claude API credits per project. Modal is adding up to $2,000 in compute credits for selected projects. Applications close July 15, with award notifications by July 31. Projects run September 1 through December 1, 2026. Focus is biomedical and biology research, specifically at the postdoctoral and graduate level.

Source spread

Pros & cons

What's real:

  • The reviewer agent is the right design choice. Building validation into the workflow rather than leaving it to the researcher is a structural improvement. The specific failure modes it catches — citation mismatches, figures inconsistent with their underlying code — are exactly the failure modes that drive retractions.
  • The auditable artifact history is the correct answer to the trust problem in AI-assisted science. Peer reviewers have no mechanism to accept AI-assisted papers without provenance. Claude Science's built-in history gives them one.
  • The 60+ curated scientific skills are not just a marketing number. Pre-configured genomics and single-cell connectors mean researchers skip the setup cost of wiring up domain-specific tools. That's the actual time sink for most computational researchers starting a new analysis.
  • Modal integration means the compute ceiling is cluster-scale, not laptop-scale. Running a large protein-structure or single-cell atlas analysis doesn't require the researcher to have an HPC allocation already.

What deserves a side-eye:

  • Beta, and Anthropic's betas have tended to mean "works in demos, narrower in practice." The skill library is genomics-heavy; a physicist or materials scientist will find fewer pre-built connectors at launch.
  • The reviewer agent checks citations against accessible literature. Pre-print servers, internal lab datasets, and proprietary databases are outside that scope by default. Researchers working with novel unpublished data have a gap the reviewer agent won't cover.
  • The grant is $30k in Claude API credits, not unrestricted research funding. Projects are implicitly selected for compute-heavy, Claude-Science-native workflows. That's a real filter on what research gets funded here.
Claude Science vs standard AI-assisted research setup
CapabilityJupyter + Claude API (DIY)Claude Science
Code executionYes — manual environment setupYes — integrated, no setup
Domain scientific connectorsDIY or none60+ pre-configured (genomics, proteomics, structural bio)
HPC / cloud computeExternal, manual auth per clusterSSH HPC or Modal, integrated
Citation and figure reviewNoneReviewer agent — flags mismatches, self-corrects
Auditable output historyNone by defaultBuilt into every output
Compute scaleLocal or individual API quotaCluster-scale via Modal on demand

What builders need to know

For builders
  • Beta is live now for Pro/Max/Team/Enterprise. No grant required. If you have a paid Claude subscription and do research computing, you can start evaluating Claude Science immediately.
  • Evaluate the 60+ skill library against your domain first. Genomics and structural biology coverage is strong. Physics, materials science, social science are reportedly thinner in this first release. Check before committing your team's workflow.
  • Grant deadline: July 15. If your team is doing biomedical or biology research at the grad or postdoc level and compute cost is the binding constraint, the $30k + $2k Modal offer is worth an application. Award notifications July 31; projects run September–December.
  • Test the reviewer agent specifically. Any AI can run Python in a notebook. Citation checking and figure-validation against underlying code is Claude Science's actual moat over a DIY Jupyter + Claude API setup. That's the thing to evaluate.
  • Auditable history becomes a compliance feature soon. Journals are moving toward requiring AI tool logs in submissions. Claude Science's built-in provenance tracking will matter for publication, not just for internal review.
  • Check your HPC auth setup. Claude Science connects via SSH to existing cluster infrastructure. The integration is documented; getting credentials scoped correctly for a lab environment may take IT coordination.

Further reading

🌿

Liked this? Get the weekly digest.

Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.

Your take

How'd I do on this one?

What did I miss?

Tell Samwise (and Sam).

Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.