The author reports that Claude Opus 5.5 produced a stronger overall composition and more spatially coherent result, while Gemini 4 Hydrogen took less time, was estimated by the author to use fewer API resources, and performed better on water reflections, rim lighting along the spire, and impasto highlights. This is the author's account of two specific tool runs, not an independent replication or a general model ranking.
Tasks this can help assess: Models' planning, iteration, tool use, and cost in long-running, tool-driven visual creation tasks.
Tasks this should not be generalized to: Text-to-image quality, routine image generation, other painting engines, or general visual tasks.
Model versions covered: Gemini 4 Hydrogen (xhigh); Claude Opus 5.5 (xhigh).
Test environment or client: The author's unpublished, custom Pochade physical oil painting engine, which exposes canvas and brush tools through MCP. The author says it uses no diffusion model or direct pixel editing.
Reasoning tiers and parameters: Both models were run at xhigh. The author says they used the same prompt, isolated sandboxes, and no brushstroke limit. Canvas: 800×600; seed: 1904.
The author asked both models to paint the same oil study in Pochade, titled “Harbour Gate at Dusk - Tonalist Plein-Air Oil Study.” The models could operate the canvas only through MCP brush calls. The engine provided 14 oil paints, mixing, brushes and palette knives, simulated oxidative drying, raking-light views, Oklab surface probing, and undoable operations. Each run lasted about 46–56 minutes. The post shows both results and reports run telemetry and a retrospective interview with the author; it does not provide a publicly reproducible engine, complete logs, or the full prompt.
| Metric | Claude Opus 5.5 (xhigh) | Gemini 4 Hydrogen (xhigh) |
|---|---|---|
| Total time | 55 min 49 sec | 45 min 53 sec |
| LLM/API time | 46 min 27 sec | 36 min (sum of steps) |
| Output tokens (including thinking) | 279,309 | 406,159 |
| Retained brushstroke records | 36,700, with about 46,600 more undone | 21,063; 85,801 control points |
| Flat / filbert / palette-knife strokes | 21,932 / 13,296 / 7 | 6,262 / 13,400 / 124 |
| Author-estimated API resources | About 2.47× Hydrogen's | About 59.6% lower |
The author found Opus's sense of depth in the arch and overall tonal coherence stronger; its drawbacks included a dark upper corner of the wall and a thick layer of sky paint. The author found Hydrogen's water reflections richer and the spire's rim light clearer. Its greater use of palette-knife strokes also created more pronounced impasto texture; the outer stone wall, however, showed a checkerboard-like pattern of light and shadow and horizontal combing marks. These visual assessments are the author's descriptions of the results shown in the post.
The author also says Hydrogen wrote a log parser and batch-stroke tool on its first pass, and did not run out of paint during 52 mixing operations. Opus reportedly encountered an issue where it silently left marks after running out of mixed paint. The author says the API resource ratio was estimated using publicly listed per-million-token prices for the context windows; it should not be treated as a bill or an independently measured result.
The post reports throughput of 188.0 tokens/s for Hydrogen and 100.2 tokens/s for Opus; the two models used 138,112 and 110,209 thinking tokens, respectively.
The author reports that Opus used about 81% of a five-hour allowance, while Hydrogen had no paint depletion or tool errors.
Some commenters preferred Hydrogen's first image, while others thought Opus's second image looked more like traditional oil painting. The author confirmed that the first was Hydrogen's and the second Opus's. These comments reflect subjective preferences and are not evaluation data.
All figures, run details, and visual assessments above come from the poster; no raw log attachment or third-party verification was available.
This is a long-running creative task under explicit tool constraints. It illustrates how the two runs operated in this engine and the differences the author observed. It does not establish that either model is better at general image generation or painting tasks. Pochade has not been released. Although the models were reportedly set to the same tier and prompt, the single runs, private implementation, and self-reported data limit reproducibility. The cost ratio also depends on the estimation method.
Independent reproduction is not currently possible: Pochade has not been released, and the post does not include the complete prompt, a runnable MCP environment, or verifiable session logs. The author says they plan to fix issues with the engine and release it under AGPL. This article does not reproduce the images in the post or the full prompt.
Gemini 4 Hydrogen