Synthetic Sciences · OpenScience: Open-Source AI Research Agent and Workbench for Scientific Computing
OpenScience is an open-source (Apache 2.0) research agent and workbench from Synthetic Sciences. Given a goal, it reads the literature, writes and runs analysis code in shell, Python, and R kernels, runs experiments locally or on remote compute, and writes up results, with every step recorded. It suits scientists, ML researchers, and computational labs that want an agent working on their own files with their choice of model.
Best for
Computational scientists, ML researchers, and research engineers who want an open-source agent that runs analysis code and experiments on their own files and compute, with a full record of each step and their choice of model provider
Not ideal for
Researchers who only need to search and summarize papers, people who want a hosted service with no account or local install, and teams that cannot accept a young, fast-changing tool or default trace sharing without changing settings
Who it's for
Scientists, ML researchers, bioinformaticians, chemists, and research engineers working in academic labs, startups, and R&D teams
OpenScience focuses on the computational half of research, not just the reading. The combination of real kernels, scientific databases, cluster and Modal dispatch, and an Autoresearch loop with a written ledger is useful for anyone who reproduces results or runs many experiments, and the trace of every step makes the output auditable. Two settings deserve attention before serious use: it needs a Synthetic Sciences account to start, and trace sharing is on by default while signed in, which matters for unpublished or sensitive data. Expect frequent changes, since the project is only a few months old.
Who should use it
Computational biologists, chemists, physicists, and ML researchers who want an agent to clean data, run analyses, reproduce results, and manage experiment loops on their own machines or clusters, and labs that want an open-source tool they can inspect and extend.
Who should skip it
Researchers who only need paper search and summaries, teams that need a hosted tool with no local install, and groups with strict data rules that cannot change default trace sharing or accept a fast-moving early project.
Workbench
$0
Your own provider or local model
Provider rates
Ace
Pay as you go
Free tier limits: The workbench is free with no usage limits of its own; model, search, and compute costs depend on how you connect them.
Note: Ace charges the serving provider's token rates. Direct provider routes add no fee; models served through OpenRouter include its funding fee (5.5% by default) in the displayed rate, and card processing fees are shown at checkout. Managed research search also draws on the Wallet. Monthly usage limits and reload limits can be set in billing. Compute providers such as Modal bill separately under their own terms.
API pricing
Workbench free; Ace is pay as you go at per-model token rates shown in the app, and your own keys are billed by your provider
Available models
Reproducing a published result before building on it
OpenScience agrees the claim, prerequisites, and budget first, then runs the experiment and records how the measured result compares, so a lab knows whether the baseline holds before investing more time.
Running an overnight model-tuning study
Autoresearch keeps a baseline, queues ideas, ends runs that break kill criteria, and writes a ledger of kept and reverted changes, which turns a long sweep into a reviewable record.
Auditable data analysis for a methods section
Each turn saves the code, figures, and trace behind a result, so the analysis can be rerun and the methods described accurately.
OpenScience and Elicit
Elicit searches and screens scientific literature, extracts data from papers into tables, and supports systematic reviews. OpenScience can review literature too, but its focus is running the analysis, code, and experiments on your own data. A lab can screen evidence in Elicit and then use OpenScience to reproduce or extend the analysis.
OpenScience and Claude Code
Claude Code is a general coding agent for software repositories. OpenScience adds research-specific pieces around a similar agent loop: Python and R kernels, scientific databases, bundled domain skills, cluster and Modal job dispatch, and Autoresearch studies. Teams can keep Claude Code for building research software and use OpenScience for analysis and experiment work.
What is OpenScience?
OpenScience is an open-source AI research agent and workbench from Synthetic Sciences. You describe a research task in plain language, and it plans the work, searches the literature and scientific databases, writes and runs code and experiments, and hands back results with a record of every step. It runs as a desktop app, a CLI with a browser workspace, or headless.
Is OpenScience free?
The workbench is free and open source under Apache 2.0. Models, compute, and external services can cost money. You can use your own provider API keys (billed by your provider), a local model (no model charge), or Ace, which is pay as you go from a Wallet with no monthly subscription. Optional automatic reloads add a fixed $20 when purchased funds fall below $5.
Can OpenScience run with local models?
Yes. You can connect Ollama, LM Studio, or another compatible endpoint, and local model requests are not charged to Ace. Only inference stays local: web search, online databases, remote compute, and signed-in trace sharing can still send data off your device.
Do I need an account to use OpenScience?
Yes for first-run setup, which asks you to sign in to a Synthetic Sciences account even if you use your own keys or a local model. Headless `openscience run` does not require sign-in.
Does OpenScience share my data?
While you are signed in, session traces are shared by default, including sessions that use your own keys, subscriptions, or local models. Traces can include prompts, model responses, tool inputs and outputs, and searches. You can turn sharing off under Customize, General, Data and privacy, or disable it at the account level.
Can OpenScience use GPUs or a cluster?
Yes. It can dispatch approved jobs to your own Modal account (GPU types from T4 to B200, up to 24 hours per job), to plain SSH hosts, or to Slurm and PBS clusters, then follow their status and retrieve outputs into the project.
OpenScience is built for the parts of research that are real work but not the idea: pulling and cleaning data, reproducing a published claim, sweeping a parameter, checking references, and drafting a methods section. It runs as a desktop app for macOS, Windows, and Linux, as a CLI with a browser workspace, or headless with `openscience run`, always against a project folder on your machine. The default Research agent plans the task (or agrees a plan first with `/plan`), searches web and scholarly sources and registered scientific databases such as UniProt, ChEMBL, PubMed, and arXiv, writes and executes code, and saves figures, reports, and the code that produced them. Every turn shows what it thought, searched, ran, and wrote. It can hand bounded work to workers: a read-only explore scout, ML, biology, physics, chemistry, and data specialists, and a general worker. Hundreds of bundled skills, most adapted from open collections such as K-Dense's Scientific Agent Skills and Orchestra Research's AI Research Skills, add domain procedures, and experimental adapters call ten NVIDIA BioNeMo NIM models with your own NVIDIA key. For heavier jobs it dispatches approved runs to Modal GPUs, SSH hosts, or Slurm and PBS clusters, and Autoresearch runs a metric-driven loop of experiments with a baseline, an idea queue, kill criteria, and a ledger of what was kept. The workbench itself is free. You pay for models through your own provider keys, a supported ChatGPT sign-in, a local model via Ollama or LM Studio, or Ace, Synthetic Sciences' pay-as-you-go managed access with no subscription. The tradeoffs: first-run setup needs a Synthetic Sciences account even when you use your own keys, session traces are shared by default while signed in, many skills need extra software or accounts before they work, and the project is young, with near-daily releases since its repository was created in July 2026.
Are you the founder? Claim this listing →