autoresearch

Autonomous iteration requires supplying a Goal, Scope, Metric, Direction, Verify, and optionally Iterations to bound the run. An interactive setup gate ensures all required context is collected before the loop starts.

The modify-verify-keep-discard loop is a deterministic iteration cycle that repeatedly modifies code, verifies results, and decides to keep or discard changes until a goal is achieved or iterations are exhausted.

Yes, you can bound autonomous loops by specifying Iterations: N in the inline configuration. This caps the maximum number of cycles to prevent unbounded execution during task automation.

Autonomous iteration uses git memory to read past iterations from git history. This contextual data guides the next steps in the loop by providing a structured log of previous modifications and outcomes.

Yes, autonomous task execution includes a dedicated security audit subcommand. This performs security checks during the iteration loop alongside planning, scenario generation, and shipping subcommands.

Bounded iterations limit execution to a specified number of cycles, meaning complex tasks may exhaust iterations before achieving the goal. If the verify step fails consistently, changes are discarded and the loop ends without completion.