Configuration
Configuration is a free-form JSON object attached to a scan. It's available to prompts
as the built-in {{configuration}} variable, and it also carries a couple of engine
settings.
Why it matters
Configuration is how you pass scan-wide knobs to your agents without hard-coding them into prompts. Your steps can read it and adjust behavior - scope, limits, feature flags - so one workflow adapts to different runs.
A typical starting value:
{
"max_files": 4000,
"include_tests": false
}
A prompt can then say "respect the limits in {{configuration}}" and the agent will see
those values. open·kritt doesn't enforce a schema - the meaning of each key is whatever
your workflow decides to make of it.
Engine-recognized keys
A few keys are meaningful to the engine itself:
repeat_runs- run the entire workflow this many times (each repeat is tracked independently). Useful for multiple passes over the same target.
Next: reserved extra.