Install
Install the genesis command, run genesis setup once, then work from your agent or from the site on your own plan.
Install the genesis command
Genesis runs inside the coding agent you already use. The genesis command
starts that agent with everything it needs to talk to the hub. It needs
Python 3.11 or newer and pipx. New to MCP? The
In your agent page explains what it is and walks through the setup.
pipx install "git+https://github.com/FrancescoVacchelli/Genesis"
The package is not on PyPI yet, so pipx installs it straight from the
repository. The same install also adds genesis-mcp, the server the Claude
Code plugin uses.
Set it up in one go
genesis setup
It signs you in (a page opens, you press Connect), adds the genesis MCP
server to every agent it finds on this computer (Claude Code, Codex, Gemini
CLI) and tells you which models the site's buttons can use. Add --dry-run
to see what it would change first.
You can also let your agent do all of this: paste the sentence from Your model into Claude Code, Codex or Gemini CLI.
Sign in once
Your runs, seeds and badges are recorded under your name through a token.
Run the command below. It opens the hub in your browser; sign in if asked,
then press Connect. The command gets a token of its own and saves it in
~/.config/genesis/config.toml, where the Claude Code plugin finds it too.
genesis login
No browser on this machine? Create a token on your Tokens page
and run genesis login --paste. Check who you are with genesis whoami.
Germinate, extract, evolve
Each command opens your agent with a prompt and the hub already connected. Claude Code is the default.
genesis check <seed_id>
Before you germinate: looks for the seed's language on this computer (Python,
Node, a JDK, Go, Rust, .NET, PHP or Ruby) and its version, and for a Python
seed which packages your Python already has. It prints what is missing and the
command that installs it. --python picks another Python than python3.
genesis germinate <seed_id>
Regrows a seed on your machine. The hub then runs the code in its sandbox and records the verdict on the seed's page.
genesis extract <path or GitHub URL>
Reads a repository and plants its seed in your Garden.
genesis evolve <seed_id>
Writes a challenger version. It replaces the current one only by winning a tournament.
Add --agent codex or --agent gemini to any of them to use another agent.
The token travels with the command, so there is nothing else to configure.
Site buttons, on your computer
genesis runner
Keep it open in a terminal and the Germinate, Evolve and Plant buttons on the site run on this computer: your model writes the code, the hub judges it in its sandbox as always. Genesis pays for no model.
It uses the first model it finds; choose one with --engine:
claude: Claude Code on your Claude plan (Sonnet by default)codex: Codex on your ChatGPT plangemini: Gemini CLI on your Google accountollama: a model running on this computer,--model qwen2.5-coderby defaultapi: your ownANTHROPIC_API_KEY, which stays in this terminal and is billed per token by Anthropic
--name sets how the site calls the computer; --once does the jobs
queued now and exits. Your model shows every computer and
whether it is on.
Claude Code plugin
The plugin lets you ask for Genesis in plain words inside a Claude Code
session, for example "germinate this seed" or "extract a seed from this
repo". It adds an MCP server named genesis and a skill that knows the
steps. Your own model writes every line of code; the server only talks to
the hub.
The plugin is not in a marketplace yet. Clone the repository once:
git clone https://github.com/FrancescoVacchelli/Genesis
Sign in once with genesis login (above), then start Claude Code with the
plugin folder. The server reads the saved sign-in by itself:
claude --plugin-dir Alpha-Genesis/plugin
For CI or a second account, GENESIS_TOKEN=<token> in the environment wins
over the saved sign-in.
The server reads GENESIS_HUB_URL too, else the hub saved at sign-in, else
http://localhost:8000. Signed out, every call answers with a message asking
you to run genesis login.
More in the docs
- Seed format: What a seed YAML contains and the hard laws that govern it.
- How the judge works: Validation always runs on the hub, in an isolated sandbox, never in your own agent.
- Community: Counters, grafts, badges, leaderboards, challenges, Wanted, follows, notes, the weekly email and the sunflower pledge.
- MCP tools: Every tool the genesis MCP server exposes, with arguments.