Run directory as memory
A run directory is a folder that holds every input, output and decision of one execution of an agent workflow. Nicholas Hopper treats the run directory as the workflow's only memory, in place of chat history or the state of any external tool.
The rule
The rules of one of Nicholas Hopper’s multi-agent repositories state it as: “Midjourney and chat history are not memory; the run directory is.” The stage document for generated artwork opens with a shorter version: “Midjourney renders; this repository remembers.”
What gets recorded
Every generated image in a run has a manifest entry with the prompt that produced it, the job id, the source URL and the SHA-256 of the exported file. Rejected candidates are listed with the reason. Exceptions made for one run are recorded in that run’s manifest, with a note that the brand files were left unchanged.
Banners are composed deterministically, so a second agent that re-runs the step produces the same bytes. The manifest stores the hash that proves it.
Why it matters
An agent that joins a run late, or replaces another agent, has no access to the earlier conversation. With the run directory as memory, it needs none. The first real run also showed the limit of the rule: its manifest notes that some rejected prompts were not captured, which is the kind of gap the rule exists to make visible.