autoresearch

Autonomous code improvement iterations are driven by providing a goal, scope, and verify command. The engine proposes small atomic changes, verifies outcomes using a numeric metric, and retains successful improvements on an isolated git branch.

Autonomous goal-directed iteration is an automated loop that modifies code, verifies the outcome, and keeps or discards changes. It progressively optimizes codebases by retaining only verified improvements based on a deterministic metric.

Yes, automated code iteration requires a Verify command that outputs a numeric metric to evaluate changes. An optional Guard command and a Scope glob to define affected files are also supported for deterministic branch isolation.

The iteration engine handles git branch isolation by creating a dedicated autoresearch branch for each run. It logs results and verifies outcomes deterministically on this isolated branch to ensure traceability and prevent untested changes.

No, a deterministic verify command is strictly required to automate codebase iteration. The engine relies on the numeric metric output from this command to decide whether to keep or discard each atomic modification.

The best way to define affected files is by providing a Scope glob during setup. This restricts the autonomous modifications to specific files, ensuring the verify command and guard checks only evaluate relevant codebase changes.