Journal Club companion • September 2026

A pulse on self-driving labs

On 23 September 2026, the Bits in Bio Journal Club put two papers on self-driving laboratories beside the daily reality of samples, instruments, failure recovery and the people who keep a lab running. This field guide accompanies that discussion.

Two papersOne Journal Club discussionA 2026–2031 outlook
36 / 57A-Lab target candidates confirmed
105 / 353executed recipes produced the target
81.8%20-step completion when every step is 99% reliable
90-second orientation

First, separate automation from autonomy.

Automation performs a procedure. Autonomy uses evidence to decide what happens next. A self-driving laboratory needs both, with boundaries that scientists can see and change.

Automation

“Run this protocol.”

The steps are defined in advance. The machine may be very capable without choosing the next experiment.

Autonomy

“Use the result to choose.”

The system senses state, evaluates evidence and selects or adapts an action inside a defined authority boundary.

Check yourself. A robot runs a fixed protocol and emails the result. Is it autonomous? No. The loop closes only when the result can change the next experimental action.
1

Plan

Question → target → experiment
2

Execute

Robots, instruments and sample logistics
3

Measure

Sensors, assays and quality control
4

Learn

Analysis → model update → next experiment
What the room saw. measurement is often the most mature link; physical execution and exception recovery remain the weakest. The field is advancing, but not evenly.
Paper result
Paper 1 • Cooper et al., 2025

A systems map for AI and robotics in natural-science laboratories

This ICRA workshop paper gives the discussion a map of the whole system. It draws attention to dependencies that a single-device demonstration can hide.

Integration & scale

Heterogeneous devices, legacy software and data systems must act like modules rather than one-off engineering projects.

Digital twins

Models of devices and workflows can support simulation, commissioning, diagnosis and explanation. Their fidelity has to be tested against the lab.

Levels of autonomy

Ask what decisions the system owns, under which conditions, and what role people retain. “Human in the loop” is a deliberate design choice.

Foundation models

Language and multimodal models can read, translate and interpret. Classical ML, optimization and control remain essential.

Standardization

Shared interfaces, data structures and laboratory objects reduce integration cost. They work only when vendors and institutions adopt them.

Responsible operation

Reproducibility, safety, sustainability, dual use and workforce skills belong inside the architecture.

Biggest strengths

  • Defines autonomy as a socio-technical system.
  • Puts humans, safety and standards beside throughput.
  • Explains why reliability compounds across long workflows.
  • Avoids treating foundation models as the only intelligence that matters.

Biggest weaknesses

  • Expert synthesis rather than systematic evidence.
  • Limited quantification by domain or lab size.
  • Economics, maintenance and change management need more empirical treatment.
  • “Democratization” remains easier to state than to deliver.

The scientific opportunity is a better division of work, with human judgement used where it earns its keep.

Paper result
Paper 2 • Szymanski et al., Nature 2023

A-Lab closes the loop for inorganic materials

A-Lab linked computed targets, literature-derived recipes, robotic solid handling, furnaces, X-ray diffraction, machine interpretation and active learning for a 17-day autonomous campaign.

Worked example. A first recipe produces no useful target phase. The diffractometer records that failure, the analysis updates the evidence and ARROWS³ chooses a different route. That change of action closes the loop.
1

Choose

Computed candidate targets
2

Synthesize

Powder dosing, mixing and heating
3

Measure

Automated X-ray diffraction
4

Adapt

Phase analysis and ARROWS³

Why it matters

A-Lab integrated the full evidence loop instead of automating one task. It also turned failures into scientific evidence: slow kinetics, model error, volatility, amorphous products and metastability became diagnoses rather than invisible waste.

What it does not prove

There was no matched human or random-search baseline. Majority target phase is not necessarily a pure, useful material. Seventeen days is not long-term operations, and one inorganic platform is not a template for every wet lab.

A common trap. Whenever a system is called autonomous, ask: autonomous over which decisions, for how long, with what preparation, under what conditions, and with what recovery path?
Meeting pulse
BiB pulse on lab automation

The room supplied the friction coefficients.

These are anonymized, paraphrased themes from the 23 September 2026 discussion. They record what this group saw; they are not a representative survey.

LayerWhat the papers anticipateWhat practitioners encounterUseful response
PlanningAI proposes experiments and mines literature.A plan fails if it does not know local inventory, SOPs, device limits or authorization.Ground models in machine-readable capabilities and explicit uncertainty.
ExecutionFlexible robots run complex protocols.Samples arrive in odd containers; consumables vary; devices jam; assays change.Normalize inputs, expose device state, design retries and exception queues.
MeasurementAutomated analytics generate reproducible evidence.Queues, calibration drift, ambiguous signals and hand-offs still dominate.Inline QC, orthogonal evidence, calibration checks and provenance.
LearningActive learning chooses informative next experiments.Objectives are unstable, multi-objective or tacit; data are sparse and biased.Bound the search and preserve scientist-defined stop rules.
Digital twinsSimulation helps plan and explain the lab.A twin of discovery biology can be confidently wrong.Start with scheduling, device state, error injection and process scale-up.
StandardsCommon interfaces enable modularity.Legacy devices, partial implementations and vendor lock-in persist.Standardize capability and data layers; maintain tested adapters.
PeopleHumans retain creativity and oversight.Trust turns on agency, space, roles, maintenance and mid-run intervention.Co-design authority, escalation and evidence review.
SafetyAutomation removes people from hazards.AI intent, translation and biased learning create additional failure modes.Use interlocks, authorization, monitoring, safe states and auditable evidence.
What the community added

Six observations from people working with the gap

These blocks collect recurring ideas from the discussion. They are anonymised and paraphrased, with no claim that every participant held the same view.

Insights from the BiB community
The loop starts before the robot deck

Several participants described assays that become automated only after someone receives the sample, fixes its metadata, adjusts the concentration and moves it into a standard plate. Map from the first uncontrolled input, or the labour simply moves upstream.

Insights from the BiB community
Discovery does not behave like a factory

A production line expects stable inputs. Assay development changes the method because the lab is still learning. That makes recovery, editable protocols and clear run state more useful than a perfect run under one fixed condition.

Insights from the BiB community
A digital twin earns trust in layers

The room trusted twins for scheduling, collision checks, liquid-handler simulation and commissioning. Confidence fell when a model claimed to stand in for novel chemistry or human biology. Fidelity has to be shown for the exact decision at hand.

Insights from the BiB community
The invisible engineer is still in the loop

Some services described as autonomous still need a software engineer to watch them and clear faults. Participants wanted remote monitoring, permissioned mid-run changes and a record that survives a restart.

Insights from the BiB community
The apprenticeship question remains open

Automation can reduce injury and free scientists from repetitive work. It may also remove the bench repetition through which junior staff learn to spot trouble. Training now needs deviation diagnosis, trace review and method validation.

Insights from the BiB community
Mundane before magical

Participants contrasted self-driving-lab ambition with laboratories that still redraw plots by hand or compare documents manually. Sample identity, metadata and routine data movement are the first layer of autonomy.

81.8%

End-to-end success

Twenty sequential steps, each 99% reliable, produce only 0.9920 = 81.8% whole-run success. Roughly one run in five fails somewhere.

P(run succeeds) = pn
reliability is multiplicative
Operational lesson. Autonomy is a recovery discipline. Checkpoints, sample identity, fault isolation, safe restart and clear escalation belong in the system design from the start.
A concrete systems example

CELISCA is the lab. MOLAR is its mobile robotics system.

Where?

CELISCA is the Center for Life Science Automation at the University of Rostock. Rostock is a city in northeastern Germany on the Baltic coast.

What?

MOLAR vehicles move trays and labware between distributed stations, including across two floors via automatic doors and elevators, under supervisory control.

Why it matters

Mobile logistics can connect valuable islands of automation without forcing every instrument into a single monolithic cell. The 2025 paper reported six integrated workstations and six months of operation.

Latest direction

CELISCA’s 2026 work coordinates a liquid handler, collaborative interface robot and mobile robot for enzymatic assays. The focus has moved from transport alone to multi-robot coordination.

Sources: Huang et al., SLAS Technology (2025), DOI 10.1016/j.slast.2024.100240; CELISCA 2026 research updates. System-specific results should not be generalized without cross-site validation.

What changed by 2026

The research has moved from heroic demos towards portable proof.

Recent work asks how to assess, observe, transfer and govern autonomous laboratories after the first system has been built.

Relatively mature

Plate-based liquid handling

Scheduled analytics

High-throughput screening

Standard sample formats

Advancing quickly

Orchestration layers

Multimodal anomaly detection

Bounded agents

Mobile logistics

Digital commissioning

Still structurally hard

Unstructured sample intake

Assay variability

General exception recovery

Cross-vendor portability

Proof of better science

Assess

ADePT

A 2026 assessment method evaluates autonomous lab robotics across adaptability and learning, dexterity, perception and task complexity.

Simulate

MATTERIX

Digital-twin work expands simulation across robots, devices, fluids, powders, heat and reaction behavior.

Orchestrate

IvoryOS

A web interface reduces the coding barrier for cross-platform workflow design and autonomous runs.

Perceive

CRESt

Multimodal sensing and vision-language diagnosis help a robotic electrocatalyst platform recognize anomalies.

Protect

Execution control layer

A proposed architecture separates AI-generated intent from authorized execution, monitoring and trustworthy evidence.

Translate

Scale-aware SDLs

Laboratory search is linked to representative devices and industrial constraints, rather than optimised in isolation.

Evidence still missing. that autonomy improves scientific outcomes across domains; transfers cheaply across sites; delivers favorable total cost for typical labs; or safely generalizes beyond bounded workflows.
Outlook
2026 → 2031

Five years of likely progress, with uncertainty left visible

Confidence is highest where standards and deployed systems already point in the same direction.

2026–2027

Instrument visibility becomes table stakes

More labs map device capabilities, states, data pathways and failure modes. Observability improves before deep autonomy.

High
2026–2028

Bounded agents enter operations

Agents retrieve SOPs, translate intent, monitor runs and prepare evidence packages; humans approve consequential actions.

High–med
2027–2029

Perception and recovery differentiate platforms

Vision and multimodal sensing move into labware verification, fault detection and recovery.

Medium
2027–2030

Digital twins narrow and deepen

Workcell, scheduling and process twins support commissioning, error injection and scale translation. Broad biological twins remain limited.

Medium
2028–2031

Multi-robot systems grow selectively

Large facilities connect specialized stations with mobile logistics. Smaller labs favor modular cells and service models.

Medium
By 2031

A tiered market persists

Capital-rich and high-throughput organisations run with more autonomy; many research labs use partial automation and shared facilities.

High

Most likely

Modular acceleration. Labs add autonomy workflow by workflow, with strong human supervision and better evidence capture.

Material risk

Platform concentration. Integration cost centralizes capability in large organizations and specialized service providers.

Plausible downside

Trust shock. A safety or provenance failure slows deployment and produces stricter authorization and liability rules.

What to do next

Start with the constraint

A staged route from a visible workflow to a bounded, evidence-producing loop.

Name the outcome

Define the scientific, quality, safety or capacity problem and measure the baseline.

Map end-to-end

Start at the first uncontrolled input and end at the first decision-ready output.

Standardize the substrate

Normalize identifiers, containers, metadata, SOP versions and acceptance criteria.

Instrument the workflow

Capture device state, calibration, timestamps, errors and maintenance context.

Automate a bounded segment

Choose repetitive, valuable and observable work with a manual recovery path.

Close one evidence loop

Let measurement select the next action inside a constrained, approved search space.

Stress-test reality

Inject missing samples, bad labels, device faults, drift and network loss.

Scale by interfaces

Add devices and agents through reusable capabilities, data contracts and continuous governance.

A good first automation project is stable enough to define, painful enough to matter, observable enough to judge, recoverable enough to operate and broad enough to relieve the real constraint.
Try the reliability test. A 30-step workflow with 99% success at each step completes only about 74% of the time, because 0.9930 ≈ 0.74. Test the whole sequence, not each device in isolation.

Questions that resist hype

  • Where does the performance denominator begin and end?
  • What human preparation and monitoring are excluded?
  • Can the run pause, change and resume with provenance?
  • What happens when a device, sample or model is wrong?
  • Which interfaces are open, standard or proprietary?
  • What evidence shows transfer beyond this site?
  • How are scientific and safety uncertainty separated?
  • What capability does the lab retain if a vendor changes?
Learn the language

Compact glossary

Self-driving laboratory

An experimental system linking planning, automated execution, measurement and iterative decision-making.

Active learning

A method that chooses the next experiment to improve a model or objective efficiently.

Orchestration

Coordination of instruments, software, data, schedules and dependencies across a workflow.

Digital twin

A computational representation of a physical asset or process, synchronized and validated for a defined use.

Observability

The ability to infer system state from logs, events, sensors and evidence.

Bounded autonomy

Autonomous decisions restricted to a validated domain, hazard envelope and capability set.

Provenance

The trace of materials, methods, versions, actions and transformations that produced a result.

Recovery

Detecting a deviation, reaching a safe state and resuming or terminating without corrupting the evidence.

Reference trail

Start with the two papers, then follow the deployment questions.

  1. Cooper, N. et al. Accelerating Discovery in Natural Science Laboratories with AI and Robotics (2025).
  2. Szymanski, N. J. et al. An autonomous laboratory for the accelerated synthesis of inorganic materials. Nature (2023).
  3. Volk, A. A. & Abolhasani, M. Performance metrics to unleash the power of self-driving laboratories (2024).
  4. Dai, H. et al. Autonomous mobile robots for exploratory synthetic chemistry (2024).
  5. Leong, S. X. et al. Steering towards safe self-driving laboratories (2025).
  6. Zhang, W. et al. IvoryOS (2025).
  7. Huang, J. et al. Mobile robots in automated laboratory workflows (2025).
  8. Canty, R. B. & Abolhasani, M. The past, present and future of self-driving laboratories (2026).
  9. Salazar-Villacis, S. & Benyahia, B. The ADePT framework (2026).
  10. Darvish, K. et al. MATTERIX (2026).
  11. Pilon, F. T. et al. A flexible and affordable self-driving laboratory (2026).
  12. Zhang, Y. et al. A multimodal robotic platform for multi-element electrocatalyst discovery (2025).
  13. Chen, L. et al. Self-driving laboratories need an autonomy safety harness (2026).
  14. Wang, Z. et al. Scale-aware self-driving laboratories (2026).
  15. SiLA 2 Standard.
  16. OPC UA LADS 1.0.

Meeting source: Bits in Bio Journal Club, “Self-Driving Labs,” 23 September 2026. Operational comments in this guide are anonymized and paraphrased. Forecasts are explicitly marked as outlook, not fact.