Build an oil painting engine with a studio of Claude Code sessions

A developer ran Claude Code sessions as engine, acceptance and docs departments to build aibrush, an oil painting engine, in 8 days and 2,300 commits; Fable 5.2 then painted a Manet copy with it.

Done withClaude CodeinGitHub· Nov 20, 2026

What they did

The poster, u/FotoRe_store on r/ClaudeAI, set the goal and made the calls at checkpoints while Claude Code sessions wrote aibrush, an open-source engine where a model paints in oil by writing Python, one stroke at a time, with simulated brush hairs, wet paint and spectral pigment mixing. The sessions were split into departments. Engine sessions each took one item from a task file, with Opus on ordinary code and Fable on brush physics. A fresh acceptance session reviewed each item by running the tests and comparing crops of its own strokes with real paintings. An editor session checked the docs against the code, and a tech session pushed accepted versions to the public GitHub repo. Handoff went through task and state files in git, never chat, and each session closed at about 200k context.

How it went

In 8 days the setup produced about 2,300 commits, 19k lines of Python, 90 test files, roughly 200 engine sessions and 290 acceptance sessions. Fable 5.2 then used the engine to paint copies of Manet's A Bar at the Folies-Bergere and the Mona Lisa, shown in a timelapse. The poster found the README decided the outcome: with the same engine and model, one test run made a good sheet with 9,777 strokes for 13M tokens and another a poor one with 970 strokes for 40M. Docs that gave recipes made the paintings more uniform, so they were rewritten to describe tools only.

Worth knowing

Painting is slow and costly: a good sheet takes millions of tokens. The API names and docs are in Russian. Many commenters called copying a famous painting pointless; the poster replied that copies are the test, and that the engine also paints from photos, sketches or text. The engine needs only Python, NumPy and SciPy.

Try it

With Claude Code· 4 parts to fill in

Act as the coordinator for a multi-session build of [the project I describe]. Set up a task file and a short state file per department in git: [engine, acceptance, docs, tooling]. For each item, open a fresh session that implements only that item and closes before [context limit]. Then open a separate fresh acceptance session that has not seen the implementer's reasoning, runs the full test suite at that exact commit and checks the actual output, such as [rendered crops compared with reference images], not just the numbers. It writes a pass or fail verdict and the next task. Hand off only through the files, never through chat. Pause at the end of each block of work and show me the verdicts before starting the next block.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related