# Optimize local application flows with runtime evidence

> Canonical page: https://codevetter.com/optimize

CodeVetter gives a coding agent a bounded loop for finding a local bottleneck, proposing one small experiment, and retaining it only when correctness and repeated before/after evidence agree.

## The bounded loop

1. Discover one executable local test or benchmark flow.
2. Measure repeatable timing, CPU, allocation, and memory evidence supported by that flow.
3. Diagnose source-backed bottlenecks while separating observation from inference.
4. Experiment with one bounded candidate and reject disproportionate patches.
5. Verify exact correctness and repeated before/after measurements before retaining anything.

The compact current path targets repository-owned JavaScript, Node.js, and Go tests and benchmarks. It does not turn a plausible edit, a noisy measurement, or a synthetic result into a production performance claim.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)