Overview
OpenResearch frames agent-assisted research as a reproducibility and attribution problem. From project ownership and experiment trees through isolated sessions, immutable source snapshots, supervised runs, compute choices, budgeted decisions, literature, and artifacts, it connects each hypothesis to inspectable evidence. The result is a local-first control model for asking what changed, what ran, and what the record supports. It improves lineage and execution visibility, but does not guarantee valid data, meaningful metrics, identical environments, or generalizable scientific conclusions.
Learning outcomes
- OpenResearch ties a hypothesis to a project, parent branch, recorded commit, run, log, and artifact, making attribution inspectable.
- Private worktrees isolate agent edits while shared Git history keeps branches discoverable; they do not coordinate every research decision.
- A completed or successful run is not sufficient evidence: inspect the source, command, effective configuration, metrics, and trajectory.
- Autoresearch uses repair, refill, promote, and stop to turn each result into a bounded next decision.
- The system strengthens lineage and execution continuity, but data validity, metric meaning, environment control, and generalization remain human judgments.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
What does OpenResearch make reproducible?
OpenResearch makes source identity, experiment lineage, execution state, and recorded output more inspectable; it does not by itself reproduce every environment or establish scientific validity.
How does OpenResearch keep agent experiments comparable?
It uses project baselines, parent-child Git branches, fixed run commands, committed snapshots, and shared evidence expectations; these expose intended variation without making remote environments identical.
Can OpenResearch run research on remote compute?
Yes, OpenResearch can send a recorded source snapshot to local, SSH, scheduled, serverless, specialized, or managed compute through adapters, while keeping the run tied to the local experiment record.
How does OpenResearch decide what to do after a run?
After reconciling terminal runs and inspecting logs and diffs, the loop repairs unanswered nodes, refills inconclusive rounds, promotes clear winners, or stops at a goal, evidence, branch, or budget boundary.
What does OpenResearch not guarantee?
It does not guarantee representative data, meaningful metrics, identical environments, controlled randomness, secure remote infrastructure, or generalization; those require separate controls and judgment.