1. Drag to Connect. Pull a wire, hover over a node, and it locks in automatically. 2. Router from Handle. Double-click any handle and a router spins up instantly. No extra steps. 3. Multi-Wire Select. Draw a box around your wires. Delete the whole mess in one go. Small changes. Big difference in how fast you can build. What feature would make your workflow feel smoother? Drop it below 👇

Drop your biggest takeaway from this classroom lesson. One sentence is enough. Now the real challenge: this workflow is not about rims. It's about placing any product in any context. A sneaker. A piece of furniture. A bag. A bike. How would you make this work for your own projects? What would you change? Share your workflow or your idea below. 👇

A small visual update to the Weavy platform: you can now select your input and output, and filters will automatically match the appropriate models. Nice use of color!

Last week I hosted a coffee hour in the morning European time. Since many of you are asleep at that time, I’m planning to host another coffee hour later in the day. I’d like to know if you’d be able to join if I schedule it around 9 p.m. Central European Time. We can talk about Weavy, general AI topics, or anything else on your mind—it’s a relaxed, open vibe. I’d really appreciate it if you can have your cameras on during the session; it’s all about getting to know each other.

The aim here is to stress-test weavy to extract a single image from a storyboard whilst keeping all details exactly the same as they appear in the the smaller grid images. I have played around with using image upscales such as Topaz with limited success. The AI seems to hallucinate and fill in details such as decals on the bike and also the bike itself. After many conversations with LLMs- in case Claude it appears that the best solution is to independently create 9 single high res images. Weavy does not like trying to extract 1 single image from a grid in one sweep- it gets confused and the details are muddled at best. I'm putting this in the community to see if anyone else has come across this issue and their workflows to resolve this.