genesis README

项目的 README,来自 github.com/EMI-Group/genesis。合并为一个 markdown 文件:README.md。

EvoX Genesis

One objective in. A software world unfolds.

Open-source AI agents for software development.
Describe the software you want. Genesis coordinates agents to build, validate, and evolve it.

Download Genesis · Website · Docs · Evidence · Paper

https://github.com/user-attachments/assets/d7f3d520-e39f-45cd-a525-77e5e8d00a75

Eighty seconds. One objective.
Watch the film on the website →

Use from a coding agent

The local MCP endpoint exposes task submission, progress, messaging and cancellation to compatible coding agents. Genesis runs the development work with its own configured models; the caller supplies context and checks the returned changes. Build this revision from source and follow the guide to configure a local credential and connect your MCP host.

See development unfold

New projects · Existing repositories · Remote development

Built with Genesis

Selected software worlds developed with Genesis.

Project What emerged Reported result
C Compiler A Rust-based C compiler built from scratch 220 / 220 c-testsuite
MESA 13 Fortran modules redeveloped in Rust 1,052 / 1,052 (0 failures) Rust test suite
tbench-wasm A software WebGL renderer in TypeScript 2,017 / 2,019 (99.90%) Khronos WebGL CTS

Latest evidence: EvoX Compiler · 2026-10-28

Explore all evidence →

The world persists. Agents do not.

Recursive Genesis agents delegate subtasks, commit changes on separate branches, and merge accepted work into main.

An objective becomes local work. Managers break down the goal, delegate tasks, and review the results. Executors implement and validate candidate changes in isolated Git worktrees.

Each task has a place. An accepted software version records what has been built; a repository path defines context, responsibility, and scope. CONTEXT.md files make these local contracts explicit.

Accepted results carry forward. The hierarchy unfolds as development proceeds. Agents finish their episodes; software versions and project history remain as the starting point for subsequent work.

Explore the architecture →

Start with an objective

Desktop app

Download Genesis → for macOS, Linux, or Windows. The website selects the installer for your platform; all published builds are available in GitHub Releases.

  1. Install and open Genesis.
  2. Configure a provider profile in Settings (API key or supported subscription OAuth), then choose its default model and, where supported, reasoning effort.
  3. Create a project or select an existing repository, then describe what you want to build.

For example:

Add rate limiting to this API. Preserve existing endpoint behavior, make the limits configurable, and add tests for requests above and below the limit.

Installation guide · Model configuration

Want to understand or operate Genesis? Open Assistant (/assistant) — Genesis Assistant understands the running system and can act on it: it reads Genesis source and inspects runtime state without approval, drives tasks and scheduler/configuration changes only after you approve the exact action, and answers in your language. See the Genesis Assistant guide for capabilities and safety boundaries.

Headless server

Run the dashboard and agent runtime on Linux (x86_64 or ARM64) or macOS (Apple Silicon):

curl -LsSf https://genesis.evox.group/dl/install.sh | sh
genesis start
genesis status
genesis update --check   # is a newer server release available?
genesis update           # install it and restart the server

Open http://127.0.0.1:9999 and configure your model provider in Settings. The server listens on localhost by default and has no built-in authentication; use an SSH tunnel for remote access.

Server installation and service management →

Provider profiles and model selection

A provider profile represents an account: its models share authentication, endpoint, concurrency, peak-hour schedules, and rate-limit backoff. Separate account IDs keep separate resource pools, even when they use the same provider and model.

In the task form, select Provider profile → Model → Reasoning effort; reasoning is a model-specific slider shown only when supported. An explicit choice locks that concrete selection for the task and its agents. Auto (by rules) leaves selection to your configured rules and defaults.

For example, in ~/.config/genesis/config.toml:

[llm]
default_provider_profile = "openai-main"

[[llm.providers]]
id = "openai-main"
provider = "openai"
auth_mode = "api_key"
api_key_env_var = "OPENAI_API_KEY"
concurrency = 3
default_model = "gpt-5"
reasoning_efforts = ["low", "medium", "high"]
default_reasoning_effort = "medium"
context_window = 200000

# Optional schedule shared by all models in this account:
peak_concurrency = 1
peak_hours = [{ start = "09:00", end = "18:00", days = ["weekdays"] }]
off_peak_days = ["sat", "sun"]
timezone = "Asia/Hong_Kong"

[[llm.providers.models]]
model = "gpt-5"

[[llm.providers.models]]
model = "gpt-5-mini"
default_reasoning_effort = "low"
context_window = 128000

Set OPENAI_API_KEY on the node running the task; do not put secrets in model rows. Nested model settings override generation, context-window, and reasoning defaults, not account authentication or capacity. The reasoning default is explicit—it is not inferred from the first effort in the list. OAuth uses account-level auth_mode = "oauth" and optional oauth_file; see subscription authentication.

The same concrete selection is available outside the task form through the MCP tool's task submission. An explicit choice locks that Provider profile → Model → Reasoning effort selection for the task and its agents, while Auto (by rules) keeps your configured defaults.

Legacy [[llm.models]] configuration remains a compatibility input; use provider profiles for new configuration. EvoGit.Config.Schema.resolve_model_spec/2 validates a programmatic selection before it is enqueued.

See Provider profiles and concrete model selection for defaults, migration, and scheduling details.

Remote development

Keep the desktop dashboard on your laptop and run agents on a server through an encrypted SSH tunnel. Tasks continue when the connection drops, and you can manage multiple remote targets from one dashboard.

Set up remote development →

Built for long-running development

Three layers: the Tauri desktop shell supervises the backend; the Phoenix LiveView dashboard exposes tasks, agents and diffs; the Elixir/OTP core schedules agents and manages Git worktrees.

Git records software versions; SQLite stores runtime and task data. Candidate changes run in isolated worktrees, with platform-specific execution controls described in the sandbox documentation.

Run from source

Use Elixir 1.20.4 and Erlang/OTP 29 to match the repository's CI environment, with Git installed.

git clone https://github.com/EMI-Group/genesis.git
cd genesis
mix deps.get
mix assets.setup
mix phx.server

Open http://localhost:4100.

Build the desktop app or use the Nix dev shell →

Benchmark your machine's I/O

Agents create worktrees, read and write files, and commit changes. Measure this workload on your filesystem:

mix bench.io
mix bench.io --dir /mnt/nvme --iterations 10 --files 500 --writes 50
mix bench.io --json > bench.json

The benchmark creates and removes its own throwaway repository without starting the Genesis runtime. Results cover worktree creation, reads and writes, Git operations, and worktree reclamation.

Research, community, and contributions

Genesis is developed by the EvoX Group at The Hong Kong Polytechnic University. For research and collaboration, get in touch. For bugs and feature requests, open an issue.

Contributions are welcome. See CONTRIBUTING.md for development guidelines and the contributor license agreement, which the CLA assistant handles on your first pull request.

Genesis grew out of EvoGit and follows the broader EvoX research lineage.

Released under the GNU Affero General Public License v3.0.

genesis (EMI-Group/genesis)

正在搜索数据库…

这是什么?Genesis 是一个开源的 AI 智能体系统,只需一个高层目标,就能构建、验证并持续演进完整的软件项目。智能体在相互隔离的 Git worktree 中工作,被接受的结果会保留下来,延续到后续工作中。
它是我需要安装的应用,还是需要导入的库?它是一个在本地运行的桌面应用,也可以选择以无界面的服务器模式运行。你描述想要的结果和约束条件,Genesis 会把工作拆分给负责规划的管理智能体,以及负责实现和验证修改的执行智能体。
我该如何让它运行起来?从 GitHub Releases 下载适用于 macOS、Linux 或 Windows 的安装包,安装并打开,然后创建一个项目,或选择一个已有的代码仓库,并描述你想构建的内容。
我需要自己的 API 密钥吗?需要。你要选择模型提供商和模型,并提供自己的 API 凭证。如果从源代码构建,还需要 Git、Elixir 1.20.4 和 Erlang/OTP 29。
服务器模式可以安全地对外开放吗?默认不可以。服务器只监听 localhost,且没有内置身份验证,因此远程访问应通过 SSH 隧道进行。
我可以把它运行在服务器上吗?可以。无界面模式可以在 Linux(x86-64 或 ARM64)或搭载 Apple Silicon 的 macOS 上运行仪表盘和智能体运行时。你可以把桌面仪表盘留在笔记本电脑上,同时通过加密的 SSH 隧道在服务器上运行智能体。
我的项目数据存放在哪里?软件版本由 Git 存储,运行时和任务数据由 SQLite 存储,两者都保存在你的电脑上。README 没有说明哪些内容会发送给你选择的模型提供商。
它能处理我已有的代码仓库吗?可以。选择一个已有的代码仓库,而不是新建项目,然后描述要做的修改。被接受的结果会成为后续工作的起点。
它如何避免多个智能体互相干扰?管理者负责拆解目标并分派任务,执行者则在相互隔离的 Git worktree 中实现并验证候选修改。CONTEXT.md 文件明确了每个任务的范围和职责。
Genesis 目前构建过什么?据报告,它的成果包括:一个基于 Rust 的 C 编译器通过了 c-testsuite 的 220 项测试(共 220 项);用 Rust 重写的 MESA Fortran 模块通过了 1,052 项测试(共 1,052 项);一个 TypeScript WebGL 渲染器通过了 Khronos WebGL CTS 的 2,017 项测试(共 2,019 项)。
作者
EMI-Group
大小
52.7 MB
星标
772
时长
1年
提交 · 90 天