The native permission prompt is hiding the moment users must approve an agent action.
Browser security behavior protects the permission boundary while the task flow needs the approval state to remain visible.
Who you’d be doing this for
“I clicked allow, then the approval disappeared and I had to start the upload again.”
Vida Salehi · Research Operations Manager
Uses Comet to collect and upload source material during recurring vendor research.
What is at stake
File-upload tasks now complete at 74%, down from 91% after a Chromium update. You have to restore completion without weakening the browser permission boundary.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- native permission integrity vs visible approval
- fast recovery vs release confidence
- visual layering vs durable task state
Why Perplexity
Comet’s supervised browser actions depend on users seeing and approving each consequential step.
Written with these in mind
Not your kind of problem? 31 more at Perplexity, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.