By running the software and getting it into an equivalent state to the original screenshot? Impressive if true.
On the other hand, if you're just "updating" the screenshot by making the AI model imagine what it would look like with some code changes - that's worse than useless; it's likely to end up generating screenshots that won't match any released version of your software at all.
Here's an example from our own docs, where you can see the captured screenshots if you scroll down to the PNGs that Promptless added https://github.com/Promptless/docs/pull/233/changes
Getting the browser navigation to work was predictably hard, but the other thing that's very hard to get right is timing when Promptless takes the screenshots. Some teams want Promptless capturing screenshots on a staging environment, and sometimes it's on prod, and different teams have different release cycles and feature flagging processes.
For that reason, we still have to do a bit of manual set-up for each user that wants screenshot updating.
Agreed though that just asking nano banana to predict a new screenshot is negative value.
So yes, there's a workflow where you really just use Promptless for the notifications. That being said, the drafting is now quite good, so it's probably at least a good starting point to get past writer's block!