OopenJiuwen-botdocs(evolve): name the single entry /evolve-design everywhere

c219f796创建于 10 天前历史提交

文件	最后提交记录	最后更新时间
explanation	docs(evolve): name the single entry /evolve-design everywhere The composer already has one entry: the algorithm picker opens only for /evolve-design and no /evolve command is handled. The docs and code comments still described the feature as `/evolve`, which reads as a second entry. Rename those mentions to `/evolve-design` in the explanation, how-to, README and REST reference pages (en and zh) and in comments. Comments and prose only; the /api/evolve/... routes are untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	10 天前
how-to	docs(evolve): name the single entry /evolve-design everywhere The composer already has one entry: the algorithm picker opens only for /evolve-design and no /evolve command is handled. The docs and code comments still described the feature as `/evolve`, which reads as a second entry. Rename those mentions to `/evolve-design` in the explanation, how-to, README and REST reference pages (en and zh) and in comments. Comments and prose only; the /api/evolve/... routes are untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	10 天前
reference	docs(evolve): name the single entry /evolve-design everywhere The composer already has one entry: the algorithm picker opens only for /evolve-design and no /evolve command is handled. The docs and code comments still described the feature as `/evolve`, which reads as a second entry. Rename those mentions to `/evolve-design` in the explanation, how-to, README and REST reference pages (en and zh) and in comments. Comments and prose only; the /api/evolve/... routes are untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	10 天前
tutorial	docs: align quick-start, deployment, and MCP guides with token sign-in URL	13 天前
README.md	docs(evolve): name the single entry /evolve-design everywhere The composer already has one entry: the algorithm picker opens only for /evolve-design and no /evolve command is handled. The docs and code comments still described the feature as `/evolve`, which reads as a second entry. Rename those mentions to `/evolve-design` in the explanation, how-to, README and REST reference pages (en and zh) and in comments. Comments and prose only; the /api/evolve/... routes are untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	10 天前

ScienceDiscovery Documentation

中文文档 | Documentation home

This is the complete English documentation set.

Tutorials

Quick start — install, start the stack, configure a model, and complete a first agent task.
Evolve a solution — run a program-evolution search end to end and judge whether the improvement is real.

How-to guides

Configure custom MCP servers: local/remote connections, secret editing, OAuth, Inspector and Session tool selection.
Deployment — local mode, Docker, and building a single-file binary from source.
Configure the network proxy — add a proxy on the settings page and choose a policy for LLM, web, and MCP traffic.
Literature research case guide — run an end-to-end cross-database literature survey, from service startup to approvals and results.
Run an evolution search — propose a /evolve-design search, size its shards, watch it run, and read the held-out result.
Install Neo4j and configure ScienceMemory — install an external Neo4j, enable ScienceMemory in system settings, and explore chains in the frontend graph.

Reference

Configuration — environment variables, default ports, upload/workspace/output quotas, and data layout.
REST API — internal HTTP API used by the UI: authentication, request/response, and error semantics.
Runtime behavior and limits — models, settings inheritance, skills, permissions, timeouts, and execution limits.
Built-in tools — parameters, boundaries, and exposure conditions for model-visible tools.
Web tools — web search/fetch providers, configuration, permissions, caching, and audit.
Repository layout — directories, modules, default ports, and data locations.
Paper Worker — PDF extraction protocol, pipeline, and limits.
Web frontend — frontend stack, event mapping, and development/test entry points.

Explanation

See the explanation index, which covers the overall architecture, control plane, agent backend, sandbox, Ascend NPU host broker, rate limiting, connectors, MCP tool protocol, network proxy, review and provenance, ScienceMemory, skill progressive disclosure, subagent orchestration, and content-addressable storage.