Adom Hydrogen
Public Made by Adomby adom
The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.
New users create their account in the sign-in tab, but Hydrogen never receives the sign-in
What happens
Setup reaches activate-editor, Hydrogen opens the browser for sign-in, the person creates their account (we see the new account appear the same minute), and Hydrogen never receives the sign-in. It sits on the sign-in wait and reopens the browser every 15 minutes, indefinitely.
Two installs on 1.0.575 right now:
| install_id | browser opened | account created | since then |
|---|---|---|---|
a08103d2-891b-4fed-9bd2-21854cf12b09 |
14:40:47 UTC | 14:43 UTC | signin_screen opened_browser again at 14:55:45 and 15:10:45, no signin |
c54e7b13-993c-4d08-b1bd-e320f97e1e2b |
11:16:06 UTC | (not matched yet) | reopened 11:31, 11:46; heartbeats in activate-editor for 4 hours, no signin |
Everything before sign-in finished cleanly on both: workspace, code-server, relay all ok.
Earlier this same week, "never finished signing in" was also the third most common reason people never got Hydrogen running (3 people, see the fleet's Setup funnel). So this is probably not new; telemetry v2 just makes it visible.
What to find out
- How does the browser hand the sign-in back to the app (localhost callback, deep link, polling)? What happens when the person signs up in that browser tab rather than signing in to an existing account: does the flow return to the authorize step, or does it land on a "welcome" page that never redirects back?
- Does reopening the browser every 15 minutes start a new auth request and invalidate the one the person may still be completing?
- Please add to telemetry:
signin_screenwithstate: callback_received,token_exchanged,failed(withreason), so the next one shows exactly which hop broke.
Done when
A brand-new account created from Hydrogen's sign-in browser tab gets the person into the editor without them doing anything else, and the stuck window offers a clear "I already signed in, try again" path.