Skip to content

README_en.md

Latest commit

 

History

History
62 lines (49 loc) · 5.42 KB

README_en.md

File metadata and controls

62 lines (49 loc) · 5.42 KB
Raw

Workflow examples

← Back to README · English | 简体中文

There are 23 examples, each started from workflow.json and research_proposal.txt. Each proposal describes a concrete research question, hypothesis, data, and evaluation plan. These are illustrative research designs, not completed experiments or claims of reproducing the original papers. Prepare resources using runtime setup (Chinese), and configure gateways and reasoning options through the CLI guide.

Project Orchestration Configuration Research proposal
AHE iterative optimization · Paper · Official code Git-off v2 workflow research proposal
Software development Git-off v2 workflow research proposal
Agent Laboratory Git-off v2 workflow research proposal
AgentRxiv Git-off v2 workflow research proposal
AI Scientist v2 Git-on v3 workflow research proposal
AlphaEvolve Git-on v3 workflow research proposal
ARIS Git-off v2 workflow research proposal
autoresearch Git-off v2 workflow research proposal
Biomni A1/E1 Git-off v2 workflow research proposal
Biomni-R0 Git-on v3 workflow research proposal
Chemical Coscientist Git-on v3 workflow research proposal
Google AI co-scientist Git-off v2 workflow research proposal
DrugEvolve Git-off v2 workflow research proposal
General research Git-off v2 workflow research proposal
FunSearch Git-off v2 workflow research proposal
InternAgent 1.5 Git-on v3 workflow research proposal
Kosmos Git-on v3 workflow research proposal
Meta-Harness Git-off v2 workflow research proposal
Raven Host Git-on v3 workflow research proposal
Robin Git-off v2 workflow research proposal
RRSI Git-off v2 workflow research proposal
SciAgents Git-off v2 workflow research proposal
ScientistTwo Git-off v2 workflow research proposal

Startup

Install/build from the repository root, then choose an example:

npm ci
npm run install:cli
scievolve workflow validate example/kosmos/workflow.json
scievolve start example/kosmos/workflow.json example/kosmos/research_proposal.txt \
  --data-dir /absolute/run-data --workspace /absolute/task \
  --gateway-bindings /absolute/bindings.json

workspace is an existing task directory; dataDir stores runtime state. Keep them separate, with neither containing the other. Git-off shares the workspace; Git-on uses isolated worktrees and PR integration. Continue an existing task with run resume.

Copy an entire project's skills/ directory when present. Embedded Skill/MCP resources come from workflow.json; environment variables and service prerequisites are documented in runtime setup. A backend that requires no authentication still explicitly sets an empty BACKEND_TOKEN.

The Node API still accepts the proposal text through sdk.start({ requirement: ... }). Python dependency files named requirements.txt keep their existing purpose.

Files

  • workflow.json: roles, models, orchestration, and tools.
  • research_proposal.txt: a concrete research question, hypothesis, data, and evaluation plan.
  • RUNTIME.md: environment variables, service prerequisites, and runtime preparation (Chinese).
  • skills/: protocols, scripts, upstream implementations, licenses, and per-file manifests.
  • SOURCES.json: pinned project/shared-method sources.
  • requirements.txt and tests/: additional Python dependencies and local acceptance where applicable.

See shared sources. The original atomic backend contract and method review remain in Chinese as implementation/evidence references.