Integrated browser creates friction for authenticated workflows

The integrated browser creates friction when a website requires authentication. This is especially relevant for knowledge workers, whose automation tasks often need an authenticated browser session.

Users can open links in an external browser, but that path is not always clear or convenient. This makes authenticated automation and UI testing harder.

No files, tests, or specific entry points are identified in the issue. Start by locating the integrated-browser and external-browser workflows, then clarify the intended authenticated-session behavior and define how users should access it and how authenticated automation can be verified as complete.

索引モデルが issue の本文から書いたものです。