@0xGky: 科研工作流也开始被 AI 整条包圆了。 开源项目 OpenScience,只要给它一个研究目标,文献调研、实验设计、写代码、论文撰写便能自己串起来。 290+ Skills,覆盖模型训练、生物信息、化学、论文写作等场景 能直接调用 Uni…

X AI KOLs Timeline 工具

摘要

开源项目 OpenScience 是一个 AI 科研工作台,输入研究目标即可自动完成文献调研、实验设计、代码运行与论文撰写,内置 290+ 技能并支持本地运行与自带 API Key。

科研工作流也开始被 AI 整条包圆了。 开源项目 OpenScience,只要给它一个研究目标,文献调研、实验设计、写代码、论文撰写便能自己串起来。 1⃣ 290+ Skills,覆盖模型训练、生物信息、化学、论文写作等场景 2⃣ 能直接调用 UniProt、PDB 等专业数据库 3⃣ 本地运行,API Key 握在自己手里,数据无须交给第三方 4⃣ 自带编辑器、终端、文件管理,浏览器打开就能用 ⚠️ 眼下缺少沙盒隔离,建议放进容器里运行。 🔗 https://github.com/synthetic-sciences/openscience…
查看原文
查看缓存全文

缓存时间: 2026/10/31 13:31

科研工作流也开始被 AI 整条包圆了。

开源项目 OpenScience,只要给它一个研究目标,文献调研、实验设计、写代码、论文撰写便能自己串起来。

1⃣ 290+ Skills,覆盖模型训练、生物信息、化学、论文写作等场景 2⃣ 能直接调用 UniProt、PDB 等专业数据库 3⃣ 本地运行,API Key 握在自己手里,数据无须交给第三方 4⃣ 自带编辑器、终端、文件管理,浏览器打开就能用

⚠️ 眼下缺少沙盒隔离,建议放进容器里运行。 🔗 https://github.com/synthetic-sciences/openscience…


synthetic-sciences/openscience

Source: https://github.com/synthetic-sciences/openscience

OpenScience

The open-source AI workbench for scientific research.

Give it a goal. It reads the literature, writes and runs the code, runs the experiments, and writes up what it found, with every step on the record.


CI npm release license

Download · Quickstart · Documentation · Changelog · Contributing


An OpenScience session comparing EGFR inhibitor potency: the trace shows the search, the written files, the analysis run and the answer with a results table

What it is

OpenScience is a research agent with a workbench around it. You describe the task in plain language; it plans, gathers evidence, runs code and experiments, and hands back results you can check. It runs as a desktop app, a browser workspace, or a terminal command, on your machine, against your files.

It is built for the parts of research that are real work but not the idea: pulling and cleaning data, reproducing a claim, sweeping a parameter, drafting the methods section, checking a reference. You keep the idea and the judgment.

  • Every step is visible. A turn reads as what happened: what it thought, what it searched, what it ran, what it wrote, then the answer. Nothing runs that you cannot see afterwards.
  • Real tools, real files. Shell, Python and R kernels, notebooks, a file system with explicit read and write grants, remote compute when a laptop is not enough.
  • Scientific reach. Hundreds of bundled skills across biology, chemistry, physics, ML and data engineering, plus connectors to databases such as ChEMBL, UniProt, PubMed and arXiv.
  • Delegation when it helps. The lead agent can hand bounded work to workers, in parallel, and keeps the synthesis and the final say.
  • Your model, your terms. Bring your own API keys, sign in to a supported provider, run a local model, or use Ace, the managed pay-as-you-go option.

Install

Desktop app. Download for macOS, Windows or Linux. It updates itself.

Command line and browser workspace.

npm install -g @synsci/openscience
openscience

Or run it without installing:

npx synsci

Or with the standalone installer on macOS and Linux:

curl -fsSL https://openscience.sh/install | bash

Then open Customize → Models and connect a provider, or from the terminal:

openscience keys add        # your own API key
openscience local add       # Ollama, LM Studio, or another local endpoint

The installation guide covers platform details, updates and uninstalling.

First task

Open a project folder and describe the work:

openscience ~/research/my-project
Inspect data/samples.csv for missing values and inconsistent labels.
Keep the original data unchanged. Save a quality report and a plot
in results/, with the code needed to reproduce them.

Start with /plan when you want to agree on the method first. For a single turn from a script or a pipeline:

openscience run "Review the analysis plan in this project"
openscience run --continue "Suggest checks for the assumptions you identified"

Review sources, assumptions, code and outputs before relying on a scientific conclusion. The agent shows you what it did so that you can.

What you can do

TaskWhat happens
Review literatureSearch scientific sources, compare findings, save cited evidence.
Analyze dataInspect inputs, write and run analysis code, produce figures and reports.
Reproduce experimentsAgree on a claim, prerequisites and budget, then compare measured results.
Run computeLocal kernels for everyday work; Modal, SSH hosts, or Slurm and PBS clusters for GPUs and long jobs, approved before they run.
Reuse proceduresBrowse the bundled skills or add a workflow specific to your lab.
Extend itMCP servers, custom agents and commands, plugins, or the TypeScript SDK.

A skill describes a procedure; it does not mean every tool or service it references is installed. Check availability in Customize before a substantial task.

NVIDIA BioNeMo

OpenScience ships ten bring-your-own-key adapters for NVIDIA BioNeMo NIM endpoints: Boltz-2, DiffDock, Evo 2, GenMol, MolMIM, MSA Search, OpenFold2, OpenFold3, ProteinMPNN and RFdiffusion. Each has a strict request schema, one approval per dispatch, and hashed artifacts written into the session; they are marked experimental and need your own NVIDIA API key under NVIDIA’s service terms. The protein-binder-design skill is adapted from the NVIDIA BioNeMo Agent Toolkit (CC-BY-4.0 skills, Apache-2.0 code), pinned at commit 0e67a61. See Scientific tools and Service credentials.

How it works

your request
  → Research agent plans, then works step by step
      → tools: shell, Python/R kernels, files, search, connectors, compute
      → workers for bounded parallel tasks (explore, general, and five domain specialists)
  → answer, with the trace and the files it produced
  • Permissions. Choose how much to ask: always, only for risky actions, or full access. Network commands ask once per destination host. Files outside the project are read or written only with an explicit grant.
  • Working folder. A conversation works in the project’s connected folder; caches and throwaway output stay in a per-session scratch space.
  • Publishing stays with you. git push, releases and uploads run from the lead session with this machine’s own GitHub and Hugging Face logins; no token is ever asked for in chat.

The capability map, Explore tools and the skills directory list what is available and how to set it up.

Benchmarks

BenchmarkOpenScience
Terminal-Bench Science (70 tasks)53/70 (75.7)
BiomniBench-DA (public 50)82.2
Terminal-Bench 4.0, science subset (14 tasks)0.714 (10/14)

GPT-6 Astra and GPT-6 Sol on Harbor, with each benchmark’s native environments, verifiers and judge. The results, with the trace of every counted trial, are in benchmarks-openscience.

Model access

OptionSetupCost
Your providerAn API key or a supported sign-in.Your provider’s billing.
Local modelOllama, LM Studio or any compatible endpoint.Your hardware.
AceSign in, choose a workspace, fund its Wallet.Pay as you go at the Wallet rate shown for each model.

Ace has no subscription. Direct provider routes add no fee; models served through OpenRouter include its funding fee (5.5% by default), already counted in the displayed rate. The card processing fee is shown at checkout.

First-run setup asks you to sign in to an OpenScience account; headless openscience run does not. Model usage through your own keys or a local model is never charged to an Ace Wallet. Details are in Models, Local models and Pricing.

Documentation

TopicGuides
First useQuickstart, Workspace, Workflow cookbook
ResearchLiterature reviews, Data analysis, Reproduction, Writing
CapabilitiesSkills, Databases, Connectors
ControlPermissions, Files, Project instructions, Configuration
AutomateCLI reference, JSON output, SDK and editors
HelpTroubleshooting, FAQ

The documentation is also available as plain text for agents: llms.txt and llms-full.txt.

Repository

backend/cli          The openscience CLI and local server: sessions, tools, providers, skills
frontend/workspace   The browser workspace (SolidJS), embedded into the CLI at build time
frontend/ui          Shared components, themes and icons
frontend/desktop     The Electron shell and its signed self-updater
frontend/docs        The documentation site
tooling/sdk          The TypeScript SDK, generated from the server's OpenAPI contract
tooling/plugin       The plugin runtime
docs/notes           Engineering notes: verification, releases, how to add a skill, tool or connector
bun run setup        # verify Bun, install, embed the workspace UI
bun dev              # run from source
bun run check        # format, typecheck and every unit suite

ARCHITECTURE.md explains how the pieces fit. CONTRIBUTING.md has the development loops, the checks that gate a pull request, and how to add a skill, connector, tool or plugin. AGENTS.md holds the conventions the code follows.

Releases

Stable releases are cut from main by the publish workflow after a full rehearsal at the same commit: packaged end-to-end tests, operating-system smokes and scientific capability canaries on every native platform. GitHub Releases carries the desktop installers, CLI archives and checksums; the changelog records what changed for users.

The desktop app updates itself. For the CLI, run openscience upgrade, or npm install -g @synsci/openscience@latest for an npm installation.

Community and support

  • Bugs and feature requests: GitHub Issues. Use the templates; a good report has a reproduction.
  • Security: SECURITY.md. Please report vulnerabilities privately.
  • Conduct: CODE_OF_CONDUCT.md.
  • Billing and account questions: use the account support channel rather than a public issue.

Acknowledgements

OpenScience is inspired by OpenCode by Anomaly and shares its commitment to excellent open-source agents. We want to bring strong, open-source scientific agents to everyone.

Most of the bundled skills come from open collections written by other people:

backend/cli/skills/ATTRIBUTION.md lists every derived skill with its upstream path and license, and each skill’s frontmatter names its original author. NOTICE carries the license texts.

License

Apache License 2.0. See LICENSE and NOTICE.

OpenScience is an independent project. It is not affiliated with, endorsed by, or sponsored by any model provider. Provider and model names are used only to describe compatibility.

相似文章

@vintcessun: 终于有人把科研AI辅助那条断头路修通了。写论文、做文献报告、出仿真图再到答辩PPT,过去每一步都得手动倒腾数据和复制结果,现在三个Skill把全流程串起来了——从scientific-toolkit算数据出图,直接喂给research-w…

X AI KOLs Timeline

报道一个科研AI辅助工具,通过三个Skill(scientific-toolkit、research-writing、office-academic)打通科研全流程,从数据计算到论文写作再到PPT制作,支持在Claude Code和Codex中一键安装,中文优先。

@ai_suxiaole: 现在很多 AI 工具都能帮科研人员省时间 但大多数只解决一个环节: 读文献、写代码、润色论文、整理摘要。 Sakana AI 的 AI Scientist-v2 它想做的是一个能跑完整科研流程的 AI 系统 从生成研究假设开始,到设计实验…

X AI KOLs Timeline

Sakana AI 发布了 AI Scientist-v2,一个端到端的自动化科研系统,能够从生成研究假设到撰写论文自动完成,并已通过同行评审被 ICLR2025 Workshop 接收。

@PierceZhang34: 分享一个专注于 AI 辅助科研的开放共建仓库 Awesome Vibe Research 项目核心目标它收集和沉淀科研全流程(从想法生成到论文发表、传播)中可复用、可验证、可演化的 AI 辅助组件,包括: Agents(智能体) Skil…

X AI KOLs Timeline

分享了一个由 ModelScope 维护的开放共建仓库 Awesome Vibe Research,该仓库收集并沉淀了科研全流程中可复用、可验证、可演化的 AI 辅助组件,包括智能体、技能包、工作流、工具和最佳实践,旨在帮助科研人员和开发者利用 AI 提升研究效率。

@gaoren7716: 写论文这件事,可能要被流程化 AI 系统重写了 不是帮你润色,不是帮你改一句话,而是从选题开始就有 13 个 Agent 在协作 功能清单: Deep Research(13-agent 调研团队) Systematic Review(P…

X AI KOLs Timeline

介绍了一套名为Academic Research Skills的开源AI工具,通过13个Agent协作实现从选题到写作、审稿的全流程学术研究自动化,可作为Claude Code插件使用,将学术研究变为标准化生产线。