Each part has one job.
The model stays simple: the extension operates, the companion explains, and Auth0 carries the authority boundary.
Session context, browsing state, and interaction stay in the browser where the agent is actually working.
The user sees who the session belongs to, which providers are connected, and whether the next action needs review.
Identity, token exchange, and approval-sensitive paths move into a hosted layer instead of disappearing inside extension logic.
What becomes legible.
The point is not more UI. It is a clean place to inspect the decisions that matter before external state changes.
The agent only acts through accounts the user has attached and can inspect in the companion.
Low-risk paths can stay fast. Drafts stay reviewable. High-risk writes can stop for approval before they commit.
Approval state, execution results, and action history land back in the same surface so the session remains understandable after the fact.
Install the extension, then inspect the boundary.
Start with the Chrome extension, then open the companion to see connected accounts, approval state, and delegated action history.