We're still auto-opening the browser for the Copilot login, so headless login won't work. Should we instead print the URL?

We're still auto-opening the browser for the Copilot login, so headless login won't work. Should we instead print the URL?

Yes. We should not try to open the browser here.

Screenshots

We're still auto-opening the browser for the Copilot login, so headless login won't work. Should we instead print the URL?

Yes. We should not try to open the browser here.

Ack, will make that change!

Done

Follow-up cleanup after merging:

• Kept the public OAuthProviderInterface shape intact, including usesCallbackServer.
• Made OAuthLoginCallbacks.onDeviceCode required. The callback object is supplied by pi, so providers can decide whether to call onAuth or onDeviceCode; callback availability should not be capability discovery.
• Made OAuthLoginCallbacks.onSelect required and documented using it for provider-driven method selection, e.g. Browser OAuth vs Device Code.
• Removed the Copilot runtime guard for missing onDeviceCode.
• Restored device-code browser opening through openUrl(). Without this, GitHub Copilot login regresses in normal non-headless environments because it previously opened the browser.
• Made openUrl() silently ignore launch failures. The URL remains visible, so headless/SSH users can still open it manually.
• Updated the custom provider docs to show method selection and the device-code metadata.

This comment is AI-generated by /wr