Guide

Getting Started

A practical entry point for understanding how BenchOS combines registry, notebook, scheduling, and Benchmate into one working system.

Start with the operating model

BenchOS is easiest to understand if you treat it as one connected environment rather than as a database plus a notebook plus a chat assistant. The registry, notebook, derived values, files, and Benchmate all operate on the same project state.

Registry records hold structured biological objects.

Notebook entries capture experimental work without losing record context.

Benchmate works directly on those same records and notes.

How a first project usually begins

A typical project starts with registering the central construct, target, assay inputs, or sample lineage. Once those records exist, Benchmate can use them to design primers, suggest conditions, attach files, and keep downstream work linked.

Create the first construct or target record.

Attach sequence files, references, and project notes.

Use Benchmate to generate the next actionable step in context.

The intended working style

BenchOS is designed for iterative work. Scientists ask Benchmate to help with the next step, but the output is expected to become part of the real system: a record update, a notebook entry, a verification result, or a reusable skill outcome.

The main shift is that useful outputs should not remain trapped in chat. They should become part of the project state.

Biology-Native Records