CanvasAgent Trains Visual Tool Agent on 140K Trajectories
TL;DR
- The paper introduces CanvasCraft, a dataset with 140K fully annotated executable trajectories and 10K RL task specifications for image creation and editing.
- CanvasAgent is trained first with SFT on executable reasoning-action trajectories, then optimized with GRPO using a hybrid outcome- and process-level reward.
- During rollout the agent inspects intermediate results, tracks visual assets, and adapts tool decisions to the evolving visual state across multi-turn interactions.
A new arXiv paper argues that hard image tasks are not really "generate one picture from one prompt" problems any more, and that the right unit of intelligence for them is a small agent that knows which tool to call, on which region of the canvas, in which order. The system, CanvasAgent, posted to arXiv in July 2026, is trained to orchestrate a heterogeneous stack of visual tools spanning synthesizing images, localizing objects, segmenting regions, editing selected content, compositing intermediate assets, reading text, and enhancing the final result, through multi-turn interaction.
The training recipe is the interesting part. The authors first apply supervised fine-tuning to teach executable reasoning-action trajectories, then optimize with GRPO using a hybrid reward that combines outcome- and process-level signals. To make that possible they built CanvasCraft, a dataset with 140K fully annotated executable trajectories and 10K RL task specifications. In the abstract's own framing, the shift is from perception-augmented reasoning to manipulation-centered visual creation, where tools "actively transform visual states rather than merely inspect them."
Why this matters if you are not training your own agents: image AI has leaned on monolithic diffusion models trying to do everything from a single prompt. An agent that inspects intermediate results, tracks visual assets, and adapts its tool choice as the canvas evolves is a different bet, closer to how a designer actually works and closer to how software teams have been building code agents. The moat starts to look like the trajectory dataset rather than the individual tools.
The honest caveat is that the abstract does not report numerical benchmarks or head-to-head comparisons against single-model editors, and it does not name the specific tools in the stack. Take the effectiveness claim as reported, not settled, until third parties reproduce it. What the paper does hand the wider community is a large trajectory dataset for a domain that has largely lacked one, and that is the piece other teams are likely to build on first.
Originally reported by paper
Read the original article →Original headline: CanvasAgent Chains 7 Visual Tools End-to-End With RL, Ships 140K-Trajectory Dataset