← Back to README · English | 简体中文
There are 23 examples, each started from workflow.json and requirement.txt. Fill in Task inputs, data, tools, and budget. Configure gateways and reasoning options through the CLI guide.
| Project | Orchestration | Configuration | Requirement |
|---|---|---|---|
| AHE iterative optimization · Paper · Official code | Git-off v2 | workflow | requirement |
| Software development | Git-off v2 | workflow | requirement |
| Agent Laboratory | Git-off v2 | workflow | requirement |
| AgentRxiv | Git-off v2 | workflow | requirement |
| AI Scientist v2 | Git-on v3 | workflow | requirement |
| AlphaEvolve | Git-on v3 | workflow | requirement |
| ARIS | Git-off v2 | workflow | requirement |
| autoresearch | Git-off v2 | workflow | requirement |
| Biomni A1/E1 | Git-off v2 | workflow | requirement |
| Biomni-R0 | Git-on v3 | workflow | requirement |
| Chemical Coscientist | Git-on v3 | workflow | requirement |
| Google AI co-scientist | Git-off v2 | workflow | requirement |
| DrugEvolve | Git-off v2 | workflow | requirement |
| General research | Git-off v2 | workflow | requirement |
| FunSearch | Git-off v2 | workflow | requirement |
| InternAgent 1.5 | Git-on v3 | workflow | requirement |
| Kosmos | Git-on v3 | workflow | requirement |
| Meta-Harness | Git-off v2 | workflow | requirement |
| Raven Host | Git-on v3 | workflow | requirement |
| Robin | Git-off v2 | workflow | requirement |
| RRSI | Git-off v2 | workflow | requirement |
| SciAgents | Git-off v2 | workflow | requirement |
| ScientistTwo | Git-off v2 | workflow | requirement |
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/requirement.txt \
--data-dir /absolute/run-data --workspace /absolute/task \
--gateway-bindings /absolute/bindings.jsonworkspace 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; set environment variables required by requirement.txt. A backend that requires no authentication still explicitly sets an empty BACKEND_TOKEN.
- workflow.json: roles, models, orchestration, and tools.
- requirement.txt: Task inputs, execution, budget, and delivery.
- 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.