Which strategies ship?
One:generic — a coding agent plus MCP gates for ideation and implementation. Both shipped modes and every benchmark run it; benchmarks differ only in the handler that scores each candidate.
Generic search
The main strategy for general problem solving. Uses Claude Code with MCP gates for both ideation and implementation.Configuration
auth_mode names the Claude Code credential source: oauth (the shipped
default — subscription login), api_key, or auto to let the adapter
resolve one. AWS Bedrock support was removed on 26 August 2026.
Gate requirements are checked before each agent is configured. warn (the
default) removes unavailable gates and logs a warning, skip removes them
silently, and error stops configuration. Unknown gate names always fail. See
Capability-Aware MCP Gates.
parent_policy controls experiment lineage. best (the default) refines the
best valid candidate; baseline starts every candidate from main. Ideation
reads from a detached worktree of that same selected ref, so its code and
RepoMemory context match the implementation base. See
Parent Selection for lineage and resume
semantics.
Usage
MCP gates
The generic strategy uses MCP gates for external knowledge access:Node structure (SearchNode)
Who evaluates and who stops?
Inkapso.evolve() the coding agent builds the evaluation and the feedback generator owns the stop decision. Benchmark runs use the same strategy but their handler supplies the official evaluation, and a handler may still cast a legacy stop vote via stop_condition().
How do I add my own?
Related
Parent selection
Which candidate to build on
Orchestrator
What drives the strategy
pip install leeroo-kapso · Every page as plain text: llms.txt.