The actual tokens might be non-deterministic, but you could look for proxy measures that are supposed to be invariant. Eg. correctness/performance on benchmarks, "thinking level" on complex problems, etc
My harness expands the prompt into a json representation that specifies layout much more rigorously, which is why you see such that amount of alignment between the two.
That internal json backing helps significantly when you want to maintain consistent design system components/patterns across multiple pages. The aligned layout is it working as intended.
Totally normal for modern models due to training on the same datasets supplied by third parties, dataset contamination, and mode collapse, especially for simple prompts that don't have enough semantic capacity. -isms are often very similar even without distillation, and tend to come and go in waves along with model generations.
Agreed. There's also a lot of bad tinging/yellow saturation that very much reminds me of early gpt-image outputs on a lot of the non-cherry picked stuff I've been seeing on Twitter/Reddit.
A lot of people were putting ZiT as a refiner downstream in early Qwen-Image 1.0 workflows, so I'm wondering if we're going to see something similar with 2.1.
Yep. I had posted a comment earlier detailing my usecases. But I too replaced that with my own system that does those same things.
It's way too bloaty, felt like operating windows start menu search.
But you might have missed so far some of the ideas they have. So it's useful to try it out, see what combination of features you use in particular and then just set those up for yourself with claude code or whatever as the LLM harness. Telegram integration is dead easy.
I ended up using QMD + custom skills to keep it up to date as new data comes in. Essentially a cross-referenced set of markdown files forming a knowledge base: https://github.com/tobi/qmd
You should open the issue with your IT department and see if they can optimize the performance. You can gather proof that GoGuardian is causing slow downs by looking at it's memory usage in the Task Manager (right click empty area in Chrome tab bar).
Thanks, completely agree. UX is probably the hardest part here. Prompting should not be a prerequisite for getting value. We have been thinking about making the system more proactive, for example surfacing relevant notes ahead of meetings or highlighting changes that need attention. Would love to hear how you think this should ideally work.
We use https://devin.ai for this and it works very well. Devin has it's own virtual environment, IDE, terminal and browser. You can configure it to run your application and connect to whatever it needs. Devin can modify the app, test changes in the browser and send you a screen recording of the working feature with a PR.
reply