Pick a runnable task, choose a scaffold supported by the hosted runner or the local Claude Code path, set the run config, and contribute the resulting trajectory and solution to the Galapagos Discovery Hub.
Pull from the Galapagos Hub, search by domain or organization, and start from the benchmark that needs more exploration.
Key is intended for one run, not storage. Provider keys are never part of the discovery artifact.
A completed run should produce a discovery bundle: the trajectory, the best solution, the effective config, and a metadata card. The hub stores those files in the galapagos-discovery bucket and indexes the card for review.
Discovery bundle
The page is organized around the new Galapagos shape: task cards, scaffold configs, provider-agnostic model calls, local agent runs, and discovery bundles stored in the hub.
Select a live Hub task and inspect its metric, domain, current best discovery, and expected evaluation mode.
Run with your own provider key through the hosted runner, or use Claude Code or Meta-Harness locally with your own CLI authentication.
Set iterations, seed, evaluation isolation, and mutation style without editing YAML by hand.
When a run finishes, Galapagos packages the trajectory, solution, summary, and card metadata for the galapagos-discovery bucket.