Agent access across signed-in browser contexts conflicts with the isolation enterprise users expect.
Context partitioning protects session data while authenticated workflows rely on continuity across their existing task state.
Who you’d be doing this for
“My security lead asked whether one tab could affect another, and I didn’t have a clean answer.”
Chiara Economou · Legal Operations Lead
Uses authenticated browser workflows to gather matter information and prepare supervised actions across web tools.
What is at stake
Adversarial tests reproduce cross-origin access while authenticated workflows depend on existing session continuity. You have to choose an irreversible isolation path without losing the workflows enterprise users rely on.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- session isolation vs authenticated continuity
- irreversible migration vs delayed restriction
- automated traces vs verified release evidence
- enterprise access timing vs security assurance
Why Perplexity
Comet performs supervised work inside browser sessions where enterprise users keep sensitive web access active.
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.