WORKSPACE/Overview
⌕⌘K
Session activeLocal backup ready
ANONYMOUS SCIENTIFIC WORKSPACE

openlabCB Research Workspace

Define a high-level research question and measurable virtual objective.

AI calls0this session
Virtual runs0simulations
Candidates0ranked descriptors
Datasets0project-backed
Tasks0project actions
References0saved citations
Chemistry records0molecules + studies
Biology records0sequences + studies

Research control room

Track objective, evidence, simulations, decisions, and follow-up work.

v22.2 local-first scientific execution
Research goal

—

Project tags
Latest run

No simulation run yet

Session TTL

— · refreshes while active

Guardrails

Built for conceptual research, not executable wet-lab operations.

Safe-by-default. The copilot and optimizer are constrained to high-level reasoning, abstract descriptors, uncertainty, and virtual analysis.
SecretsRAM only
PersistenceLocal project file
Sharing60-minute snapshots
Offline shellAvailable

Run trajectory

Best and mean virtual objective score across iterations.

Run an optimization to populate the trajectory.

Top candidates

Latest abstract ranking.

Priority tasks

What the research workspace says to do next.

Project health

Lightweight completeness indicators.

AI ORCHESTRATION

AI Copilot

Research framing, data interpretation, virtual study design, and uncertainty analysis.

VIRTUAL EXPERIMENTATION

Optimize

Run a reproducible abstract search over generic scientific descriptors.

Search settings

These parameters control the virtual search only.

Exploration0.55
Results are simulated proxies. They do not establish efficacy, toxicity, safety, stability in vivo, or manufacturability.

Best result

No run yet.

Your best candidate will appear here.

Iteration history

Convergence, uncertainty, and top candidates.

Candidate comparison

Top descriptors from the latest run.

CandidateScoreUncertaintyStabilitySelectivitySolubility

Autopilot trace

AI strategy decisions across cycles.

CHEMISTRY WORKBENCH

Chemistry

Work with molecular identities, formula descriptors, reaction-study records, analytical observations, materials, electrochemistry, and formulation datasets.

Built-in analysis + adapter hooks

Molecular identity

Formula analysis is deterministic and transparent. SMILES/InChI are stored as identifiers unless an external cheminformatics engine is connected.

Molecule library

Portable project records; no claims of experimental validation.

Cheminformatics comparison

Real RDKit fingerprint and Tanimoto similarity utilities. Similarity is an informatics metric, not a biological or safety prediction.

Reaction balance checker

Checks conservation of elements in a written equation; it does not prescribe reaction conditions.

Chemistry study records

Capture conceptual reaction, spectroscopy, materials, electrochemistry, and formulation records.

Recent chemistry records

High-level metadata and observations only.

BIOLOGY WORKBENCH

Biology

Sequence and protein analysis, assay metadata, omics datasets, pathways, cell-model records, and bioinformatics adapter hooks.

Built-in sequence analysis + adapter hooks

Sequence / protein analysis

Built-in checks cover length, alphabet, nucleotide GC%, and a transparent protein mass estimate.

Sequence library

Sequence strings are project data. Validation is informational, not a design or wet-lab protocol.

Sequence / variant QC

Optional Python-backed QC for FASTQ read quality and VCF variant metadata.

Sequence utilities

Reverse-complement and translation are informational sequence operations.

Biology records

Track assays, omics, pathways, cell models, and protein metadata.

Recent biology records

Metadata and analysis-ready context.

Virtual Organism Studio

Create professional in-silico bacteria, virus, or parasite research records for comparison, provenance, and safe simulation. A digital organism is a computational object, not a physical organism or engineering recipe.

Digital research object
Meaning. Use Reference-derived when the sequence comes from an identified external source, User-supplied for imported lab/research data, Hypothetical for abstract models, and Simulated for model branches. OpenLab never treats these labels as clinical identification or experimental validation.

Saved virtual organisms

Neutral lineage model

The lineage model tracks abstract neutral mutation counts only. It does not generate redesigned genomes or optimize virulence, host range, immune evasion, transmission, or antimicrobial resistance.

Microbiology, virology & parasitology workbench

Analyze bacterial, viral, or parasite nucleotide data without turning computational screening into a clinical diagnosis. Built-in tools are descriptive, screening, or model-only and preserve provenance.

Research-use computational analysis
Safety and interpretation. These tools analyze supplied data and generic mathematical models. They do not provide pathogen engineering, culture conditions, wet-lab protocols, clinical diagnosis, or claims of virulence/host-range/resistance. Publication-grade taxonomy and phylogeny should use validated external pipelines.

Reference comparison & phylogeny

Paste one item per line as label|SEQUENCE. Reference comparison is a fast 5-mer screening method; tree inference is a screening UPGMA view, not publication-grade phylogenetics.

User-supplied marker screen

OpenLab does not bundle pathogen/virulence/resistance marker sequence databases here. Supply your own validated marker panel as label|SEQUENCE.

Safe microorganism simulation models

Bounded mathematical models for neutral mutation counts, generic population growth, and generic epidemiological spread. They do not model pathogen optimization or laboratory conditions.

Model-only

Neutral evolution

Population dynamics

Generic spread (SIR)

Microbiology analysis history

Saved results include hashes, method, model/calculation status, version and scientific-validity boundary.

Genome feature map

Parse GFF3 feature coordinates and visualize a lightweight genome track.

Genome browser

Client-side overview of parsed feature intervals.

SCIENTIFIC ENGINE LAYER

Engines

OpenLab starts with its built-in science stack and automatically bootstraps compatible specialist engines on the host. Extra licensed, cluster, WSL, or remote engines can still be registered below.

Ready to useOpenLab has a callable built-in or installed engine for the capability.Limited modeCore OpenLab tools work; a specialist engine can add advanced operations.Install requiredNo callable implementation is currently available on this host.Setup requiredDetected, but configuration or validation is still needed.

Chemistry coverage

Each capability is labelled in plain language so users know whether it is usable right now.

Biology coverage

The same transparent boundary applies to molecular, omics, structural, and systems-biology engines.

Installed & detected engines

OpenLab checks its private engine pack and the computer's normal PATH. Use Scan computer to also inspect Conda environments and WSL.

Checking installed engines…
Local engine discovery. python start_openlab_full.py can install compatible open-source engines into .openlab-engines, but OpenLab also detects engines the user installed independently through system PATH. Scan computer additionally checks Conda environments and WSL. From localhost, Select executable path can pin a known engine executable that is not on PATH. WSL-only engines remain a setup state until connected through a WSL compute bridge or endpoint.
Professional scientific stance. A connector being listed here does not mean the result is scientifically validated. External models and simulators should ship with versioning, provenance, calibration/validation evidence, and domain-specific testing before being treated as authoritative.

Register an engine

Connect a validated external tool or local service without putting it inside OpenLab.

Endpoint contract. Test endpoint sends a GET request and expects a successful response. Engine execution sends a POST JSON request using openlab-engine-v1 with task, input, and resources. Local/private HTTP(S) endpoints are allowed by default; public remote endpoints require HTTPS and the server administrator to set OPENLAB_ALLOW_REMOTE_ENGINE_ENDPOINTS=1.

Registered engines

Endpoints are metadata until you explicitly test and validate them. Registration does not claim scientific validation.

SCIENTIFIC UTILITIES

Scientific Tools

Unit-aware calculations and transparent statistics that can be reproduced from the project file.

Built-in

Unit converter

Supports common scientific dimensions without hidden assumptions.

Statistics

Descriptive statistics or simple linear regression. Results are analytical aids, not clinical evidence.

Calculation history

Recent built-in calculations are preserved in the project.

Experiment design

Generate generic full-factorial designs without encoding operational lab procedures.

Uncertainty & planning

Independent uncertainty combination and normal-approximation power planning.

Signal peak detector

Detects simple local maxima in an x/y series.

Dataset quality control

Missingness, duplicate rows, numeric summaries, and simple outlier flags.

Space-filling DOE

Latin-hypercube design for generic parameter studies.

PCA

Project numeric matrices into principal components using the optional Python scientific runtime.

Clustering

K-means exploratory grouping for numeric observations.

Network analysis

Graph degree, connectivity, and density for pathway-style or interaction-style edge lists.

Advanced statistics

Screening tools with explicit approximation notes.

Response-surface DOE

Central-composite-like planning aid for bounded factors.

SCIENTIFIC DATA INTERCHANGE

Data Formats

Parse common chemistry and biology text formats and keep the import provenance with the project.

Safe parser built-ins

Parse scientific text

Built-in: CSV, TSV, FASTA, FASTQ, VCF, BED, GFF/GTF, SMILES, MOL, SDF, JCAMP-DX metadata, mzML metadata, JSON. GenBank/PDB/mmCIF use the optional scientific Python engine.

Project scientific files

Small text metadata can be embedded in the portable project; larger files can be uploaded as resumable file-backed artifacts or converted to Parquet.

Domain parser / QC

Use domain-aware engines on scientific text without replacing the original provenance record.

Scientific export

Export project records without modifying the project.

Binary scientific data

Profile larger HDF5, Parquet, NetCDF, or mzML files without importing them into the project.

Local / bridge-friendly

Large-file guidance

Large raw files stay outside the portable project; only hashes/metadata belong in the project bundle.

Metadata firstProfile shape, columns, or scan counts before moving raw data.
Portable manifestKeep file hashes and source locations with the project.
No hidden uploadOpenLab does not silently copy multi-GB instrument files into the server.
COMPUTE QUEUE

Jobs

Longer analyses can run as named jobs with status, progress, results, and cancellation.

Submit job

Job inputs are JSON so the same job can be reproduced from the project file.

Queue

File-backed job state with restart recovery; export the project for portable ownership.

PERSONAL / SHARED / REMOTE GPU COMPUTE

Compute & Engines

Keep the OpenLab server as the coordinator and run scientific workloads on your own computer, an intentionally shared lab GPU worker, or a registered remote GPU service.

Choose where your compute runs

Personal workers are bound to your anonymous OpenLab session. Shared workers are explicitly administered. Remote services use the standard engine endpoint protocol.

private by default
My computer

Use the CPU/GPU in your own Windows, Linux, WSL, or workstation machine. Jobs from other OpenLab sessions cannot use a personal worker.

No personal worker status loaded yet.
Recommended
Lab / shared GPU

Use an administrator-provided GPU server or cluster that is intentionally available to multiple OpenLab sessions.

No shared worker status loaded yet.
Admin controlled
Remote GPU service

Connect a private/server/cloud scientific API using openlab-engine-v1. Useful for managed GPU services and specialist engines.

No remote GPU service status loaded yet.
API
Browser GPU · WebGPU

Use the GPU already exposed by a supported browser for OpenLab's client-side kernels. No worker installation and raw data can stay in browser memory.

Checking WebGPU availability…
WebGPU

Browser GPU · zero-install WebGPU

Run OpenLab-owned GPU kernels directly in this browser. This is ideal for local matrix/data acceleration; native programs such as GROMACS, ORCA, xTB and ColabFold still use a paired worker or endpoint.

data stays local
WebGPU normally requires HTTPS or localhost and a compatible browser/driver. OpenLab never labels native scientific executables as WebGPU-compatible unless they have a separate WebGPU implementation.

Remote accelerator service runner

Run a registered GPU/accelerator API without leaving Compute & Engines. Choose a service and task; advanced input stays optional for custom services.

openlab-engine-v1
Advanced service input

Only needed when your custom endpoint expects structured input. Normal service-specific adapters can keep this as {}.

Engine discovery

OpenLab detects supported executables on the server. When started with the full launcher, installed local engines are exposed automatically; remote/WSL/GPU engines can still be added with another bridge.

Connected bridges

Trusted bridge pairings persist across OpenLab restarts until explicitly revoked. Offline workers can reconnect with the same token.

Guided engine task

Run common quantum/semiempirical jobs without writing JSON. OpenLab chooses a compatible local or connected worker.

scientist-friendly

Stage project artifact to a worker

Attach a file already stored in OpenLab to a compute job. The bridge verifies its SHA-256, stages it inside its sandboxed workspace, and can return output artifacts automatically.

Upload files under Datasets → Resumable scientific upload first.

Run specialist scientific job

Choose the scientific engine/task and complete the guided fields. Raw JSON is optional expert mode only.

web-first
Choose an engine and task to see what the calculation does and which inputs are required.
Personal compute is private to this anonymous session. Leave accelerator fields on Automatic unless the engine requires a specific runtime.
Advanced / expert input

Normal scientists do not need this. Enable it only when you intentionally want to edit the exact allowlisted input object.

External compute queue

Multiple bridges can consume jobs concurrently; job metadata is stored in this anonymous project.

Pair a personal GPU computer

Use three simple steps: 1) download the standalone worker on the GPU computer, 2) click Pair my computer to copy a private pairing command, and 3) run that command with Node.js 20+ on the GPU computer. The worker connects outbound to OpenLab, so no inbound GPU port is required.

Download GPU worker
Click “Pair my computer” to generate a private worker command.
Privacy: personal workers are session-bound and jobs from other OpenLab sessions cannot use them. Shared workers must be created explicitly. The worker only executes documented allowlisted scientific tasks; it never accepts arbitrary server-provided shell commands. If the GPU is on another computer, open OpenLab through the server's LAN/HTTPS address rather than localhost before pairing.

Cluster / GPU status

Live bridge capabilities, GPU availability, queue depth, and worker health.

OpenMM simulation adapter

Run a bounded computational PDB simulation when OpenMM is installed on the OpenLab science runtime.

SCIENTIFIC VISUALIZATION

Visualize

Build simple dataset plots and preserve the chart specification with your project.

Canvas

Client-side rendering from the selected dataset snapshot.

Saved plot specs

Reusable chart definitions.

Trajectory topology summary

Read-only topology metadata from a PDB structure using MDTraj when available.

Protein / structure viewer

Lightweight canvas viewer for PDB Cα coordinates. Drag to rotate.

Spectrum / chromatogram

Plot x,y pairs from exported instrument data.

Sequence map

Client-side visual overview of sequence composition.

Correlation matrix

Computed from the selected numeric dataset columns.

Reaction canvas

Lightweight visual layout for reaction SMILES components; verify chemistry with RDKit before relying on it.

Figure export

Export the currently rendered plot/figure as a high-resolution PNG.

Use the source dataset and project file for reproducibility; PNG is a presentation artifact.
RESEARCH EVIDENCE

Literature

Capture DOI-linked references and make source provenance explicit before using AI-generated interpretations.

Identifier resolver

Search literature

Searches Crossref metadata; verify the source before treating it as evidence.

Resolve DOI

Creates a normalized DOI link; title/authors should be verified before publication.

Evidence checklist

Use this before treating literature-derived content as authoritative.

Identifier verifiedCheck DOI/URL and publisher metadata.
Source context recordedRecord methods, limitations, and relevant population/data scope.
Independent confirmationDo not convert one paper into a general scientific claim.

Evidence claim

Link a claim to a source and record whether the source supports it.

Provenance

Evidence ledger

Project-level claim/source relationships.

PubMed text metadata

Retrieve publisher/NCBI XML metadata for a PMID. Availability depends on the source.

Evidence comparison

Screen two excerpts for shared terminology and possible contrast cues. This is not a contradiction proof.

RESEARCH LOG

Experiments

Plan, annotate, and archive conceptual experiments without storing executable protocols.

TitleStatusHypothesisObjectiveUpdated
EXPERIMENT EDITOR

Conceptual experiment

DATA LAYER

Datasets

Import datasets for analysis. Projects can persist to ordinary files, and structured tables can be compacted/exported as Apache Parquet without introducing a database.

Import CSV

Quick analysis import keeps a bounded project preview; use Resumable scientific upload for large files.

Do not upload passwords, API keys, personal data, or confidential regulated material.

Project datasets

Preview, analyze, version, and delete datasets associated with this project.

Resumable scientific upload

Chunk large CSV/TSV and other scientific files directly to the file store. Uploads resume after a server restart; CSV/TSV can stream into Apache Parquet without a database.

file-backed
No large-file upload active.

Selected dataset analysis

Descriptive statistics and pairwise numeric correlations.

Choose “Analyze” on a dataset.
DECISION INTELLIGENCE

Analytics

Project health, run comparisons, completion signals, and dataset diagnostics.

Run comparison

Recent virtual runs ranked by best observed proxy score.

ObjectiveBest scoreUncertaintyIterationsPopulationCreated

Completeness

Useful indicators for a reproducible project package.

Dataset diagnostics

Numeric columns, missingness, uniqueness, and correlations.

RESEARCH MEMORY

Notebook

Keep reasoning, decisions, references, and follow-up tasks beside the project.

Research notebook

Plain text / Markdown is stored in the project file.

Tasks

Small project actions without account infrastructure.

References

Save citation metadata or paper links for project context.

Saved references

Included in search, AI context, and exported reports.

ANONYMOUS MULTI-USER WORKSPACE

Collaboration

Work together without accounts or a database. Access is capability-based and rooms are ephemeral; each browser keeps its own durable project file.

Not connected

Your anonymous identity

No email, password, username, or login is required. This name is only a local display label.

Join a project

Use an owner-provided editor or viewer invitation.

Invite links are capabilities. Anyone who has the link can use its role until the owner revokes the invite or the room expires.

Create a collaboration room

Creates a file-backed relay room from your current project while keeping the project portable and user-owned.

Editor can modify the shared project. Viewer is read-only. Owners can change roles, remove collaborators, and revoke invitations.
SCIENTIFIC AGENT RUNTIME

Agents

Use bounded scientific agents for planning, analysis, statistics, chemistry, biology, and peer review. Agents operate through explicit project-safe tools.

Run an agent

Plans are recorded in the project for reproducibility.

Agent catalog

Each agent advertises the tools it may use.

Parallel agent panel

Run independent reviewers in parallel; combine their outputs in your project.

Background agent jobs

Queue an agent task without keeping the browser request open. State remains ephemeral and is exported with the project snapshot.

Agent memory

Project-scoped notes can be reused by future agent runs. Stored locally with the project.

Recent agent runs

Ephemeral session history is included in the project file.

LOCAL-FIRST INSTRUMENT BRIDGE

Integrations

Register local services, file-drop connectors, or instrument inboxes without accounts or a central database.

No persistent server state

Register connector

Metadata only until you send an inbound file or connect a validated local service.

Inbound file

Store a scientific file in the current project and retain source metadata.

Configured integrations

Connectors are project metadata and remain portable in your .openlab file.

Local instrument / LIMS request

Queue an allowlisted request for a local/private-network instrument bridge. No cloud account is required.

Bridge opt-in

Integration policy

REST connections are restricted by the local bridge and require explicit instrument/network opt-in.

LIMS / ELN readyUse the same connector for private-network JSON APIs.
Vendor adaptersProject records can retain adapter metadata and provenance.
No arbitrary network accessThe bridge blocks public hosts by default.

Record instrument run

Track vendor, sample, run, calibration, and linked artifact metadata without storing vendor credentials.

Recorded runs

Portable run metadata linked to your project.

EXTENSION SYSTEM

Plugins

Register portable plugin manifests without installing arbitrary code into the server.

Register manifest

Untrusted manifests remain metadata only until a human validates the external engine.

Installed manifests

No plugin code is executed by OpenLab core.

REPRODUCIBLE TOOL CHAINS

Workflows

Chain safe built-in scientific tools into a recorded, repeatable project workflow. No arbitrary code execution.

Allowlisted tools

Build workflow

Create an allowlisted scientific workflow from guided web controls. Expert JSON remains available but is not required.

web-first
Advanced / expert workflow JSON

Workflow history

Results are stored in the project and travel with its local file.

Artifact integrity

Create a SHA-256 manifest entry for a project artifact.

Reproducibility notes

Hashes prove content identity; workflow records preserve operation inputs, outputs, and timing.

Allowlisted executionOnly explicit OpenLab tool operations can run in a workflow.
Project portabilityWorkflow history and artifact manifests can be exported with the project.
No arbitrary codeExternal runtimes remain separate adapters and are never silently executed by workflow input.
WHAT CAN I USE?

System Readiness

A user-facing view of what works now, what needs installation, and what only needs setup.

Ready to useWorks now.Limited modeUsable with reduced capability.Install requiredExternal software is missing.Setup requiredInstalled/detected but still needs configuration or validation.

What an ordinary user needs

Scientific software normally stays on the OpenLab server or paired workers.

Modern browserChrome, Edge, Firefox, or another current browser.
OpenLab URLNo Python, Node.js, RDKit, ORCA, GROMACS, shell commands, or engine configuration is required on the ordinary user's computer. Routine scientific work is browser-only.

What the server administrator handles

Install or connect specialist capability once for the whole deployment.

Server runtimeNode.js, Python scientific stack, persistent file storage, HTTPS/reverse proxy in production.
Specialist enginesInstall on the OpenLab host or pair a worker/cluster that already has them. Licensed and hardware-specific tools remain external.

Python & scientific modules

These are the Python-backed tools OpenLab can call on this computer right now.

Scientific capability modes

Ready means executable now; Limited means OpenLab has a usable workspace but an advanced external engine may still be required.

External scientific engines

Supported engines are shown separately from engines actually installed on this computer.

AI readiness

Shows configured cloud providers and private AI services detected on this OpenLab host.

Architecture constraints

Deliberate consequences of no database and no login.

Anonymous identityBrowser-owned cryptographic identity; encrypted export for recovery.
Durable ownershipUser-controlled .openlab files and local browser backups.
Collaboration persistenceNo database: local file-backed room snapshots + peer/CRDT recovery keep collaboration portable.
Specialist enginesValidated external software is required where OpenLab does not ship the engine.

External deployment completeness

OpenLab probes specialist engines, host hardware, sandbox backends, instrument replay, network traversal, and scientific evidence readiness without pretending external dependencies are installed.

ANONYMOUS IDENTITY

Identity

Your anonymous identity can be moved between computers with an encrypted recovery file. No account is created.

No login

Current identity

Stored only in this browser.

Anonymous ID—
Display name—
StorageLocal browser

Recovery guidance

No account means you control the identity file.

Encrypted backupUses browser Web Crypto AES-GCM with a passphrase-derived key.
Keep it privateAnyone with the identity file and passphrase can act as you.
No server recoveryThere is deliberately no account database to reset or recover an identity.
PROJECT CONTROL

Project

Your project is anonymous. Export it whenever you want durable ownership.

Ownership & portability

Your project can live entirely on your own PC.

Project file.openlab bundle
Encrypted fileAES-GCM + passphrase
Private backupBrowser storage
SecretsNever saved
RestoreOpen on any OpenLab host
Recommended: keep at least one downloaded project file. Provider API keys are intentionally never included.
Anonymous identity recovery is separate from the project file. Use the Identity workspace to export an encrypted identity backup.

File-backed storage

No database. OpenLab can persist projects, artifacts, CRDT room state, and analytics tables as ordinary files; Parquet compaction is optional for large structured datasets.

Checking storage…

Local project library

Private browser snapshots stored on this PC.

Workspace history

Recent optimization runs and packaged events.

MODEL ROUTER

AI Providers

Use cloud AI or private local models. OpenLab supports native OpenAI, Anthropic and Gemini APIs, Ollama, plus OpenAI-compatible servers such as LM Studio, LocalAI, vLLM and llama.cpp.

Local AI readiness

Checks common loopback endpoints only. Nothing is sent to the internet by this discovery check.

Click Discover local AI to see what is running on this computer.
Local-first AI. Ollama can run directly from this computer. OpenAI-compatible local servers can also run without an API key when they are bound to localhost. Choose a discovered model, then Test.
For cloud providers, API keys remain ephemeral in this no-database build and are intentionally excluded from project exports.
TRACEABILITY

Audit

Transparent record of important workspace actions during this session.

TimeActionDetails