Local AI critique goes live
Critique and recompose now belong inside the default composition loop. The point is not novelty. The point is helping people ask for better feedback earlier.
The right moment for AI is before certainty
Most creative tools add AI as a late-stage button. We wanted the opposite. Critique is most useful when a layout is still flexible enough to change.
That means the system should be close enough to the canvas that asking for help feels like part of arranging, not a separate workflow entirely.
What actually changed
Canvas now treats critique and recompose as core interactions: upload, arrange, ask, revise. TARX handles the local intelligence underneath it, so the product can keep the loop private and immediate.
Critique helps you see what is not working. Recompose helps you move faster when you already know the intent but need a better arrangement.
Together, they make the product feel less like a passive board and more like a responsive local studio.
Why local matters here
If every critique request had to leave the machine, the interaction would feel heavier. Latency would matter more. Privacy would matter more. Pricing pressure would matter more.
Local TARX routing does not solve every problem, but it does solve the worst product habit: making feedback feel scarce.
What we are not claiming
Critique is not a substitute for taste. Recompose is not a promise of perfect design. The system is meant to help you see alternatives and move faster, not erase judgment from the process.
The best version of AI in Canvas is supportive, fast, and easy to ignore when you already know what you want.
The real product win
When critique goes live inside a local-first product, people stop treating AI like a special event. It becomes part of normal craft. That is the bar we care about much more than a marketing demo.
Download Canvas and try the local critique loop for yourself.