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 :'(
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!
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.
tl;dr. I'm one of the founders of Promptless, the AI agent that automatically updates docs. 12 months ago, we decided to give our agent a tool to let it "scream" when it was struggling, and we wanted to share our learnings and some cool examples of issues that it caught.
A (charitable) interpretation of this is that the model understands "stuff that would embarrass Anthropic" to just be code for "bad/unhelpful/offensive behavior".
e.g. guiding against behavior to "write highly discriminatory jokes or playact as a controversial figure in a way that could be hurtful and lead to public embarrassment for Anthropic"
https://promptless.ai/blog/technical/i-must-scream