Browser control: allow explicit credential handoff for localhost development

What feature would you like to see?

Add an explicit, user-approved way to hand a selected browser credential to a localhost development environment. This could be a one-time copy or injection flow scoped to a specific origin, rather than unrestricted cookie-store access.

Use case

While testing a local application in Codex Desktop, the app may need the same development authentication token as an already signed-in browser profile. Browser control can operate the authenticated page but cannot pass that credential to the local stack, even when the user explicitly approves it and both the source and target are development environments. This prevents true UI-to-backend end-to-end testing.

Suggested safeguards

• Disabled by default
• Explicit user confirmation for each handoff
• Source and destination origin shown in the confirmation
• Optional localhost-only restriction
• Never print the credential in the task transcript or logs
• Short-lived, revocable grants

Codex Desktop on macOS.

No file or test is named. Start by tracing the browser-control credential handling and the Codex Desktop localhost development flow on macOS. Done means an explicit, origin-scoped handoff exists with confirmation, safe credential handling, and the listed restriction and revocation safeguards.