Git branch model
Each experiment runs in its own git branch, inheriting code from its parent experiment. This enables:- Isolation: Each experiment starts from a clean parent state
- Inheritance: Child experiments build on parent solutions
- Versioning: All code changes are tracked
Experiment session
TheExperimentSession manages a single experiment:
Implementation flow
One session does the whole build.run_implementation renders the implementation prompt — the problem, the chosen solution, the knowledge context and the repo memory — and hands it to the coding agent with the budget’s deadline:
<code_changes_summary>, <evaluation_script_path>, <evaluation_output>, <score>, <technical_difficulties>). Errors are not retried inside the iteration; they become feedback for the next one.
Result structure
Each experiment is recorded as aSearchNode — solution, branch, evaluation tags, judged feedback and score. The full field list is on the search strategies page.
Session finalization
After an experiment completes:- Commit changes to the experiment branch
- Push to origin (available for child experiments)
- Record cost from coding agent
- Cleanup session folder
Related
Execution flow
The loop around one experiment
Coding agents
Who writes the code
pip install leeroo-kapso · Every page as plain text: llms.txt.