Heureka Labs
Get Bench

Contents The lab

05

Running the lab

Autonomous labs, inventory, colonies, provenance, schedules — the operational half of research, in the same app as the science.

The Lab is where Bench stops being a notebook and starts being an instrument for running a group. It holds the record collections a lab depends on: what you have, what you are breeding, where a result came from, and what should happen next Tuesday whether or not anyone remembers.

Every Lab space shares one engine, so they behave the same way: searchable, importable, file-attachable, shareable with your team, with an activity trail of who changed what. And ARC can read and edit all of them through a structured path that cannot corrupt the underlying file.

The four record spaces share the same search, import, file-attach and sharing behavior.
SpaceHoldsThe thing it answers
Autonomous labA research question, worked on continuously“What did the lab find while I was away?”
InventorySupplies, reagents, equipment“Do we have any, and where is it?”
AnimalsColonies, cages, breeding“What is in the colony this week?”
Data SpacesDatasets and how they relate“What else have we seen this in?”
ProvenanceEntities and their lineage“Where did this result come from?”
05.01

Autonomous labsBeta

A lab that works on your research question around the clock, inside your project, and checks every result before it tells you.

On the beta channel only.

People ask

  • What is an autonomous lab?
  • Does the lab keep working when my computer is off?
  • Will the lab run experiments on its own?
  • How do I pause or stop a lab?
  • How much does an autonomous lab cost?

Describe what the lab is for in your own words (a grant aim, a question, a project) and attach the files that matter. The lab turns it into questions and works through them: it analyzes your data, tests hypotheses and checks every result, and keeps going when your laptop is closed. Everything it makes lands in the project like your own work, in Data/, Code/, Analysis/ and Drafts/.

You get a brief, not a stream. The lab writes a short brief on what changed and why it matters. Choose when you hear about it: every day or every week at the hour you pick, or only when the lab needs you. The brief is always on the lab page and in lab/brief.md.

It proposes; you decide. When data cannot settle a question, the lab writes up the experiment that would, with its plan. Approve it, ask for changes or decline it. You run it in your lab and add the results to the request, and the lab analyzes them against the plan it wrote.

Every step is on the record. Read what the lab did by question, or step by step with search, a page at a time; each step links to the ones it builds on. The same record is in lab/timeline.md. Message the lab at any time, attach a file or a paper, or ask it to Catch me up.

Follow a lab from wherever you are.
BenchWeb and iPhone
Set up a labYes—
Read the brief and the recordYesYes
Approve or decline a requestYesYes
Message the lab, Catch me upYesYes
Pause, resume, stopYesYes

Pause keeps everything and starts nothing new; resume when you like. Stop ends the lab for good, and its brief, record and files stay in the project. Add a Stop if condition and the lab pauses itself when it is met.

Each lab runs on a seat, monthly or annual, from Plan & Usage, with or without Heureka Unlimited. The lab's own work is included in the seat. Checks with other frontier models are optional and use credits, up to a monthly limit you set.

05.02

Inventory

Supplies, reagents and equipment — with structures drawn automatically.

Import what you already keep in a spreadsheet and it works immediately; there is no schema to design first. Search across it, attach files to a record, export back out to xlsx, and share the whole inventory with your team.

Any column called SMILES, Structure, InChI or InChIKey renders the molecule above the text — no new column type, no migration. An existing chemicals list lights up the moment you import it.

Ask ARC to look something up or make a change — "we are out of the 2 mM stock", "move everything in freezer B shelf 3 to shelf 4" — and it edits the records directly, routed through the same sync and activity trail as your own edits.

05.03

Animal colonies

Animals, cages and breeding — matings, litters, weaning, archiving.

A colony manager for animal research: track individual animals and cages, set up matings, record and wean litters, archive animals when they leave the study. An overview dashboard shows the state of the colony, and an activity trail records who changed what.

Genotype-due and maximum-age flags are computed against the correct date rather than drifting with the clock, so the flags and nudges you rely on fire consistently.

Colonies sync per entity, so two people editing different parts of the same colony do not collide, and every change is attributed to the person who made it. ARC can add animals, move a cage or update genotypes on request through the same safe path.

05.04

Provenance

Every result traceable to its source — recorded as the work happens, not reconstructed afterwards.

A map of how your animals, samples, reagents, experiments and datasets connect. The important part is that ARC records lineage as it works: make a plot from a table and the link is captured with no prompting and no discipline required from you.

Browse it as a list or as a graph, click any entity to jump to where it actually lives, and generate a methods note with a provenance table straight from a record's lineage. Suggested links surface connections the agent believes exist but has not been told about.

This is the answer to the question every reviewer, auditor and future postdoc eventually asks: where did this number come from?

05.05

GeneSummary

A page for every human gene, CpG site and microRNA, inside Bench.

People ask

  • What is GeneSummary?
  • Can I look up a gene in Bench?

The same pages as genesummary.com: what a gene does, where and when it is expressed, its clinical associations and pathways, each with its confidence and source. Pathway, tissue and disease pages link it all together, and a back-and-forward trail lets you follow links as far as you like.

Follow a page to hear in the feed when it changes or someone adds a claim; like it, or add a claim of your own with its evidence. When ARC mentions a gene, CpG site or microRNA in chat, the name is a link to its page, and the Open in Heureka Bench link on genesummary.com opens the page here.

05.06

Scheduled tasks

Work that should happen on a cadence, with or without you.

Set a task to run on a schedule — a weekly QC sweep over new data, a monthly digest of what changed, a nightly check on an inbox folder. It runs in the project, writes its result to disk as a file, and posts a notification when it is done.

Schedules can be per project or across the workspace, and are listed together so you can see everything that is going to happen without opening each project.

05.07

The Activity board

Upcoming, Running, Needs you, Done — everything the agent is doing, on one board.

Every agent action becomes a card: background analyses, drafts, document reviews, scheduled runs, cloud jobs, even chat sessions. At a glance you can see what is in flight, what finished while you were away, and what wants your attention.

You stay in control from the board itself — cancel a run in progress, retry one that failed, open a finished result straight in the editor, or dismiss cards you are done with. Run agent launches a background task in any project, or across the whole workspace, without opening a project first.

Below the board sits a calmer Updates stream: recommendations, nudges and announcements, deliberately separated from the live work.

05.08

Shared with the team

An inventory or colony is a shared record, not a copy each.

Lab spaces can be shared with your team, with collaborators seeing the same records and the same activity trail. Renaming a shared inventory or colony renames it for everyone — the registry updates first, so collaborators and the mobile app see the new name rather than the old one.

If you are not on the owning team, Bench says so plainly instead of renaming only your local copy.