Overview
Target configuration controls stimulus and rollout generation behavior. In bgit, targets are configured in theTARGET section of your input.yml file.
Naming Best Practice: Always provide a
name field for your targets. bgit appends a hash to target names (e.g., my_target becomes my_target_abc123def456) to ensure uniqueness. Named targets are easier to identify in recipe.yml and when referencing them in bake configurations.Configuration Fields
Name
Target name identifier. Recommended: Always provide a descriptive name.If omitted, defaults to
target. The name will be hashed (e.g., coding_target_abc123def456) to ensure uniqueness.Generators
List of generator configurations. See Generators.
Model Configuration
The model that will generate the sample responses during rollout. Optional - defaults to This specifies which model is used to generate responses to your stimuli during the rollout phase. If omitted, bgit will automatically use the
PARENT_MODEL for sequential bakes if not specified.PARENT_MODEL from .bread (set after previous bakes) for sequential baking workflows. Using the parent model allows you to preserve the characteristics and behavior from previous bakes in your model evolution chain.Generation Parameters
Maximum tokens to generate per response
Generation temperature (0.0-2.0). Higher = more random/creative.
Number of trajectories (responses) to generate per stimulus
Performance
Maximum concurrent API requests during rollout
Advanced
Additional arguments passed to
chat.completions.create()Complete Example
Field Reference Table
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
generators | Array | No | [] | List of generator configs |
model_name | String | No | PARENT_MODEL | Model that generates sample responses during rollout (defaults to PARENT_MODEL to preserve characteristics from previous bakes) |
max_tokens | Integer | No | - | Max tokens per generation |
temperature | Float | No | 1.0 | Generation temperature |
num_traj_per_stimulus | Integer | No | 1 | Trajectories per stimulus |
max_concurrency | Integer | No | 10 | Max concurrent requests |
extra_kwargs | Object | No | {} | Additional model params |
Minimal Example
The simplest target configuration:Prompts are configured separately: Prompts are defined in the
PROMPT section of your input.yml, not in the TARGET section. See Prompt Configuration for details.