Yeah, the current approach basically makes this entirely a non-starter for the target audience (eliminate a critical control for people for whom critical controls are a pain point).

Uploading your 2FA tokens to a third party is also likely a non-starter, sorry.

You don't need to upload your 2FA tokens somewhere. Everything runs on your local machine. You can do whatever you want there.

In future versions it will be possible to do the same with, for example, your Google SSO sign-in and 2FA enabled. The reason for the limitation is that we simply wanted to get it out into the world and see if anybody is as excited about it as we are.

For reference, the azure client, opens a browser for the login, which redirects to a dns address that equates to "localhost" on a port that will effectively get the final auth tokens to the local instance, which then persists and shuts down the service. Should be able to do very similar.

Have you looked at Cerby?