Skip to main content

Overview

Search strategies control how Kapso explores the solution space. They generate solution candidates, run experiments, and track results.

Available Strategies

The main strategy for general problem solving. Uses Claude Code with MCP gates for both ideation and implementation.

Configuration

The generic strategy deliberately keeps bedrock as its default authentication profile. Set auth_mode to auto, api_key, or oauth to opt into another Claude Code credential source. The deprecated use_bedrock boolean is still accepted for compatibility. 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: Advanced strategy for benchmarks that explores solutions as a tree structure.

Algorithm

Each iteration:
  1. Prune: Remove unpromising solutions (after 20% budget)
  2. Expand: Generate new child solutions from selected nodes
  3. Select: Pick best nodes to experiment with
  4. Run: Execute experiments in parallel

Configuration

Parameters

Exploration vs Exploitation

Node Structure (SearchNode)

Strategy Comparison

Creating Custom Strategies