autoresearch

Autoresearch turns Claude Code into a relentless iteration machine. You set a goal, point it at your codebase, and it runs a modify-verify-keep-or-discard cycle until the goal is met or you pull the plug. Inspired by Karpathy's approach to autonomous ML research, it generalizes that pattern to any domain where you can write a test for success.

This isn't a framework you build on. It's a skill you add to Claude Code, so setup is dropping it into your skills directory. The work happens inside the loop: it proposes a change, runs your verification, and only keeps what passes. You define what done looks like, then walk away.

Solo developers and researchers who already live in Claude Code get the most here, a way to throw a well-scoped, testable problem at an agent and let it grind. Teams without a clear success signal get less, because the loop is only as good as the check it runs against.

The catch: it lives entirely inside the Claude Code ecosystem, so you need that subscription. And autonomous iteration burns API credits fast. Give it a fuzzy goal or a slow test and it will happily spend your money chasing its tail. Scope it tight and watch it.