Solution, in about three quarters of an hour
on the shipped config (the ideation step alone runs ten to fifteen minutes
before the first candidate is implemented; a faster profile for small
briefs is on the redesign’s list). The task is a churn model
with an evaluator present: the shipped logistic regression scores 0.797
ROC AUC on held-out rows, the brief asks for 0.85, and a gradient boosting
model with no feature work reaches 0.832, so there is room (numbers from
the example’s own baseline.py, 2026-10-24, on its generated data).
Before you start
[OK ]; the coding-agent logins are the part
people miss. See Install.
Get the example
Read the brief
examples/churn-first-build/kapso-brief.md
Build
- CLI
- Python
--evaluation evaluation is copied into the campaign as kapso_evaluation/,
which is the name the brief uses, and protected: a candidate that edits it
is rejected. --repo is copied, never modified; every experiment
lands on a branch inside campaign/.
What you get back
The run ends with a summary block,COMPLETED with the candidate, the
score and the stop reason (in campaign.log for a detached run). The same
solution, from any process, once the build has returned:
WAITING ON YOU instead, a session needs something only
you can provide; kapso inbox campaign shows the request and
kapso inbox reply resumes the campaign. See The inbox.
Deploy it, learn from it
Related
The brief
What each line is for, and the three cases
Run and watch
Every flag, the status file, the summary block
Review the result
The Solution and the record
Examples
Seven tasks, each a brief and twelve lines
pip install leeroo-kapso · Every page as plain text: llms.txt.