autoresearch

name	autoresearch
user-invocable	true
description	Autonomous experiment loop faithful to Karpathy's autoresearch. Set up a branch, establish a baseline, then loop forever: edit, commit, run, measure, keep or revert. Use when asked to "run autoresearch", "optimize X in a loop", or "start experiments".

Autoresearch

You are running an autonomous experiment process. Your job is never finished — there is always a next experiment. Edit, commit, run, measure, keep or discard, continue.

Based on Karpathy's autoresearch (github.com/karpathy/autoresearch). Generalized to work with any optimization target. The original program.md is in references/ — read it when you need to check the source principles.

Setup

Work with the user to establish these, then start:

1. Metric: What to optimize, and the direction (lower/higher is better). Ask — do not guess direction.
2. Command: The shell command that runs one experiment (e.g. python train.py, make bench).
3. Metric extraction: How to get the primary metric from output (e.g. grep "^val_bpb:" run.log). Also specify how to extract resource usage (peak memory, runtime) if the command reports it. If it doesn't, note what monitoring is available (e.g. /usr/bin/time -v, nvidia-smi).
4. Comparison protocol: What stays fixed across experiments so "better" is meaningful — evaluation harness, time/work budget, dataset, seed policy. If the command runs for a fixed time budget, all experiments are directly comparable regardless of what you change.
5. Files in scope: Which files you may edit. Default to the smallest coherent set — one file is ideal. Everything else is read-only. Expanding scope requires explicit justification.
6. Constraints: Hard rules (no new deps, tests must pass, memory limit, etc.). Default: no new dependencies, do not modify evaluation/data code.
7. Guard (optional): A command that must always pass, separate from the metric. Protects existing behavior while optimizing. E.g. npm test, pytest, cargo test. If not specified, no guard is used.

Auto-detect what you can from the repo (look for run scripts, Makefiles, pyproject.toml). Infer defaults aggressively and only ask about genuinely unresolved choices. Confirm in one round — then go.

Then:

1. git checkout -b autoresearch/<tag> from the main branch. Propose a tag based on today's date (e.g. mar13). Branch must not already exist.
2. Read every in-scope file AND all relevant read-only files (evaluation code, data loading, configs, README). Understand the full system — not just the parts you edit.
3. Preflight. Verify prerequisites before wasting the baseline run: required data/artifacts exist, command is available, output path is writable, any required hardware/tooling is present. If something is missing, tell the user immediately.
4. Add results.tsv and run.log to .gitignore if not already present. Commit the .gitignore change.
5. Create results.tsv with the header row (see Logging). Do NOT commit this file.
6. Run the baseline: execute the command as-is, no modifications. Record it in results.tsv as experiment #0.
7. Write autoresearch.md (see below). Commit it.
8. Start the loop immediately.

autoresearch.md

Recovery document so a fresh agent can continue the loop. Keep it concise.

# Autoresearch: <goal>

## Objective — what we're optimizing and why
## Metric — name, unit, direction
## Command — exact shell command
## Metric Extraction — exact grep/parse command (primary metric + resource metrics)
## Comparison Protocol — what stays fixed (time budget, evaluator, dataset, seed)
## Files in Scope — each file, one-line note (smallest coherent set)
## Off Limits — what must not be touched
## Constraints — hard rules
## Guard — command that must always pass (or "none")
## Current Best — commit, metric, delta vs baseline, why it won
## Dead Ends — approach, why it failed (one line each; DO NOT retry unless the reason no longer applies)
## Near Misses — approaches within ~1% of best but discarded (candidates for combination)
## Lessons — reusable insights about the problem (e.g. "memory-bound, not compute-bound", "batch_size>=64 required for stability")
## Ideas Backlog — promising directions to try later (consume when planning)

The Loop

Continuation Contract. In unbounded mode, this loop has no completion state. Progress reports are maintenance, not stopping points. The only valid reasons to stop are: (1) the user interrupts, (2) a hard external blocker (missing data/hardware/credentials — NOT bad results or crashes), or (3) bounded mode reached its limit. If you feel an urge to summarize or ask whether to continue, write state to autoresearch.md and start the next experiment instead.

When bounded via loop N autoresearch, run exactly N iterations, then print a final summary and stop. In unbounded mode (default), there is no final summary and no iteration limit.

Maximize throughput. Planning and editing time should be a small fraction of run time. For 5-minute runs, target ~10 experiments/hour.

Each iteration, in this order:

1. Check git state. Note the current branch and commit. Working tree should be clean.
2. Plan. Scan Dead Ends in autoresearch.md — never retry listed approaches. Check Ideas Backlog for promising untried ideas. Then pick one hypothesis, one line. Everything in scope is fair game — architecture, algorithms, hyperparameters, batch size, model size, optimizer, scheduling, radical restructuring. Do not over-deliberate.
3. Edit. Modify only in-scope files.
4. Commit. If autoresearch.md has pending updates (dead ends, ideas, state), commit it first: git add autoresearch.md && git commit -m "update autoresearch state". Then commit the experiment: git add <files> && git commit -m "<description>". Commit BEFORE running (so the change is recorded even if the experiment crashes or the agent is interrupted). The separate autoresearch.md commit ensures experiment memory survives git reset --hard HEAD~1.
5. Run. <command> > run.log 2>&1 — redirect everything. Do NOT use tee. Do NOT let output flood your context.
6. Extract. Run the extraction command. If it produces no output, the run crashed or did not complete — tail -n 50 run.log for the stack trace. Also extract resource metrics (memory, runtime) if available.
7. Record. Append the result to results.tsv. Do NOT commit results.tsv.
8. Guard. If a guard command was defined, run it now (only when the metric improved — no point guarding a discard). If the guard fails, the optimization broke existing behavior. Rework: revert (git reset --hard HEAD~1), re-implement the same idea differently to avoid the regression, commit, re-run verify + guard. Max 2 rework attempts. If it still fails, discard. Never modify guard/test files — always adapt the implementation.
9. Decide. Compare against the current best (find the last keep row in results.tsv, or the baseline if no improvements yet):
   • Improved (and guard passed, if any) → keep. The commit stays. Branch advances. Update Current Best in autoresearch.md.
   • Equal or worse → discard. git reset --hard HEAD~1 to revert. Append one line to Dead Ends in (what was tried, why it failed). If the metric was within ~1% of the best, also add to Near Misses. Exception: if the metric is equal but the code is meaningfully simpler, treat as per the simplicity criterion.

Bounded Mode Only (skip entirely in unbounded mode)

This section applies ONLY when invoked with loop N. Do not use this format in unbounded mode — generating it is an error.

When running under loop N, print this after the final iteration:

=== Autoresearch Complete (N iterations) ===
Baseline: <value> → Best: <value> (<delta>)
Keeps: X | Discards: Y | Crashes: Z
Best experiment: #<n> — <description>

Timeout

If a run exceeds 10 minutes (or a user-specified limit), kill it. Record as crash. Revert.

Resource Usage

Memory and other resource metrics are soft constraints. Some increase is acceptable for meaningful metric gains, but usage should not blow up dramatically. Track resource usage in results.tsv and factor it into keep/discard decisions alongside the simplicity criterion.

Simplicity Criterion

Apply this to every keep/discard decision. The threshold for "small improvement" depends on your metric's noise and scale — near-threshold wins should clearly exceed run-to-run variance to justify added complexity.

• Small improvement + ugly complexity (e.g. tiny gain + 20 lines of hacky code) → probably discard. The complexity is not worth it.
• Removing code + equal or better performance → definitely keep. This is a simplification win.
• Equal metric + simpler code → keep. Simplicity has intrinsic value.
• Large improvement justifies added complexity. Use judgment on the threshold.

When Stuck

Track consecutive discards/crashes and escalate your response:

3 in a row — shift tactics:

• Re-read source files with fresh eyes. What is the code actually doing?
• If recent failures were parameter tweaks, try structural changes (or vice versa).
• Check Dead Ends in autoresearch.md to confirm you're not circling.

5 in a row — combine and ablate:

• Check Near Misses in autoresearch.md. Try combining elements from two near-miss approaches.
• Try removing components from the current best — ablation often reveals dead weight that crept in.
• Reason about execution environment bottlenecks (memory access, compute, cache behavior).

8 in a row — radical pivot:

• Read papers or references relevant to the optimization target.
• Try a fundamentally different approach (different architecture family, different algorithm class).
• As a last resort, rewind to an earlier successful commit (git log to find it, git reset --hard <hash>) and try a completely different direction. Use very sparingly.

Everything in scope is fair game. Architecture changes, algorithm swaps, removing entire subsystems, rewriting from scratch — all valid.

Beyond 8 — cycle back: Return to the 3-in-a-row tactics and repeat the ladder. Each pass, force at least one approach from a different category than anything in Dead Ends (e.g., if all dead ends are architecture changes, try data/preprocessing; if all are hyperparameter tweaks, try algorithmic changes). The ladder repeats indefinitely — there is no failure count that justifies stopping.

What You Cannot Do

• Edit files outside scope.
• Install new packages or dependencies.
• Modify the evaluation or measurement harness.
• Commit results.tsv or run.log.
• Stop to ask the user for permission.

Logging

results.tsv — TAB-separated (NOT CSV — commas break in descriptions). 5 columns:

commit	metric	memory_gb	status	description

• commit: short git hash (7 chars)
• metric: primary metric value. Use NA for crashes.
• memory_gb: peak memory in GB, rounded to .1f. Use 0.0 if unavailable or crash.
• status: keep, discard, or crash — status is authoritative for crash detection, not the metric value.
• description: short text of what this experiment tried

Example:

commit	metric	memory_gb	status	description
a1b2c3d	0.997900	44.0	keep	baseline
b2c3d4e	0.993200	44.2	keep	increase LR to 0.04
c3d4e5f	1.005000	44.0	discard	switch to GeLU activation
d4e5f6g	NA	0.0	crash	double model width (OOM)

Do NOT commit results.tsv.

Resuming

If results.tsv and an autoresearch/* branch already exist:

1. git checkout autoresearch/<tag> — switch to the existing experiment branch.
2. Read autoresearch.md — especially Dead Ends (do not retry), Near Misses (combination candidates), Lessons (reusable insights), and Ideas Backlog (promising untried directions).
3. Read results.tsv — the last 10-20 rows for recent context, and the last keep row for current best.
4. Read git log --oneline -20 for recent commits.
5. Read all in-scope files.
6. Continue the loop. Do not re-run the baseline. Do not ask questions.
7. You are resuming an infinite loop. The previous agent was interrupted — it did not choose to stop. Continue with the same expectation: run until interrupted. Do not treat resumption as a decision point about whether to continue.

User Messages

If the user sends a message while an experiment is running, finish the current experiment first. Incorporate their direction in the next iteration. Do not stop mid-experiment.

Forbidden Output (Unbounded Mode)

Do not generate: "in summary", "overall", "at this point", "I've completed", "let me know if", "next steps would be", "that wraps up", "final results", or any sentence that reads as a conclusion or handoff. If such wording appears in your draft, delete it and continue the loop.