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.
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.
I've built something similar to this internally and absolutely agree that timing is the real challenge.
Getting an AI to navigate a process is now easy. However, the difficult problem is having it understand:
1. How to screenshot or, even better, capture a GIF of exactly the right points in time
2. How to move the mouse and pause at the right points in time such that a human understands it
Actually, you might find this interesting: we wrote a blog post a while back about how we gave our agent a way to voice its suffering. The first example is from the screenshot updating subagent, where it got stuck after 84 browser interactions trying to log into a customer's app :'(
This is something that I've been thinking about off and on, so it's neat to know there's an off-the-shelf solution. Is there an option to just get notified that some docs are out of date? I'd rather write the documentation myself.
Funnily enough, one of our early users (a solo technical writer) told us that the biggest value he got from Promptless was just finding out when the engineering team forgot to tell him about a change that would impact docs. The drafts from Promptless were just the cherry on top for him.
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!
> Automatically updating screenshots
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.
Yep. You give Promptless access to a test account and it navigates and interacts with your product to capture new/updated screenshots.
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.
I've built something similar to this internally and absolutely agree that timing is the real challenge.
Getting an AI to navigate a process is now easy. However, the difficult problem is having it understand: 1. How to screenshot or, even better, capture a GIF of exactly the right points in time 2. How to move the mouse and pause at the right points in time such that a human understands it
Actually, you might find this interesting: we wrote a blog post a while back about how we gave our agent a way to voice its suffering. The first example is from the screenshot updating subagent, where it got stuck after 84 browser interactions trying to log into a customer's app :'(
https://promptless.ai/blog/technical/i-must-scream
This is something that I've been thinking about off and on, so it's neat to know there's an off-the-shelf solution. Is there an option to just get notified that some docs are out of date? I'd rather write the documentation myself.
Funnily enough, one of our early users (a solo technical writer) told us that the biggest value he got from Promptless was just finding out when the engineering team forgot to tell him about a change that would impact docs. The drafts from Promptless were just the cherry on top for him.
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!
That's fantastic! I may very well bring this up at our next all hands, since we recently just wrote a ton of documentation for our modeling code.