git404hub

what is writing-driven-autoresearch fr?

happyhappy-jun/writing-driven-autoresearch — explained in plain English

Analysis updated 2026-05-18

16PythonAudience · researcherComplexity · 4/5Setup · hard

tl;dr

A three-agent AI system that wrote and submitted a full research paper in about three hours, winning first place at an ICML hackathon.

vibe map

mindmap
  root((repo))
    What it does
      AI agents write a paper
      Files not chat handoffs
      Ph vs phm verification
    Tech stack
      Python
      LaTeX
      Bash
    Use cases
      Autoresearch prompts
      Multi-agent coordination
      Verified number tracking
    Audience
      Researchers
      AI agent builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Study a real example of multiple AI agents dividing research work with strict file-based handoffs instead of chat.

VIBE 2

Reuse the agent prompts and paper writing rules to run a similar automated research process on a different topic.

VIBE 3

Learn a verification pattern that forces every number in a generated document to be either deleted or backed by real measured data.

what's the stack?

PythonLaTeXBash

how it stacks up fr

happyhappy-jun/writing-driven-autoresearch920linjerry-stack/capital-studioadya84/ha-world-cup-2026
Stars161616
LanguagePythonPythonPython
Setup difficultyhardeasyeasy
Complexity4/53/52/5
Audienceresearcherresearchergeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1day+

This is a run record and prompt set, not an installable tool, reusing it requires your own GPU fleet and Overleaf setup.

in plain english

This repository is the complete record of a multi-agent system that wrote an academic research paper from start to finish in about three hours, winning first place and 10,000 dollars in OpenAI credits at a hackathon judged by eleven expert reviewers. Almost every file in the repository, including the experiment code, the paper itself, and a running log of decisions, was written by AI agents rather than a human. The only file a person wrote is the README. Three separate AI agents split the work with strict boundaries. One agent owns the overall clock and makes decisions but runs no code. A second agent owns the experiments, running models on GPUs and saving results as JSON files, but never touches the paper. A third agent owns the paper itself and never touches a GPU. The agents never talk to each other in chat. Instead, everything that crosses from one agent to another is written to a shared folder of files, including a status file and a decisions log, so nothing important depends on a message being remembered correctly. The core method is to write a complete, submittable draft of the paper before any experiment has produced real results, using two special markers in the paper's text: one for a number that is still just a guess, and one for a number that is backed by an actual measured result saved on disk. A script checks every measured number against its backing file, and another script fails the process if any guessed number is still present when the paper is due. This forces every claim in the final paper to be either deleted or backed by a real result, while still letting the team keep a paper that could be submitted at any moment as the plan changed underneath it. The repository includes the three agent prompts, the paper specification and style guide, a detailed project plan with a planned response for every possible experimental outcome, the full decision log, and the verification scripts. The authors present it as something to copy and adapt for running the same kind of agent driven research process on a different project and topic.

prompts (copy fr)

prompt 1
Explain how the master, experiment, and writing agents divide responsibilities in this writing-driven autoresearch project.
prompt 2
Help me adapt the master.md, experiment.md, and writing.md prompts from this repo for my own research project.
prompt 3
Show me how the ph and phm LaTeX macros in this repo enforce that every number in a paper is either real or removed.
prompt 4
Walk me through the decision ledger in ralph/DECISIONS.md to understand how the agents handled a failed hypothesis.

Frequently asked questions

what is writing-driven-autoresearch fr?

A three-agent AI system that wrote and submitted a full research paper in about three hours, winning first place at an ICML hackathon.

What language is writing-driven-autoresearch written in?

Mainly Python. The stack also includes Python, LaTeX, Bash.

How hard is writing-driven-autoresearch to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is writing-driven-autoresearch for?

Mainly researcher.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.