Original issue tinyhumansai#2466 by @StatoCritico on 2026-05-21T21:40:26Z
Summary
After completing OAuth login (Google or GitHub) in the browser, the callback page at api.tinyhumans.ai/auth/<provider>/callback shows the "Opening OpenHuman in a few seconds..." page with an Open OpenHuman button. The button triggers a deep link openhuman://auth?token=<JWT>&key=auth, but the OpenHuman app ignores it and stays on the welcome/login screen.
Environment
- OS: Windows 11 24H2 (build 26200)
- OpenHuman version: 0.54.0
- Browser: Chrome (latest)
- Runtime: "Esegui localmente" (Run locally)
- UI language: Italian
Steps to reproduce
- Open OpenHuman desktop app
- On the "Benvenuto in OpenHuman" screen, click
Seleziona un runtime → choose "Esegui localmente" → continue
- Click
Google (or GitHub) to start OAuth
- Complete login in browser
- Browser redirects to
api.tinyhumans.ai/auth/<provider>/callback?... and shows the "Opening OpenHuman in a few seconds..." page
- Click
Open OpenHuman button
- Expected: the app receives the token and logs the user in
- Actual: nothing happens. The app remains on the welcome screen.
Same behavior with Google and GitHub OAuth providers.
Diagnostic data
- Protocol handler is correctly registered in
HKCU:\Software\Classes\openhuman\shell\open\command:
"C:\Users\AppData\Local\OpenHuman\OpenHuman.exe" "%1"
- The local runtime is listening on
127.0.0.1:7788 and responds with:
{"api_server":"https://api.tinyhumans.ai","name":"openhuman","ok":true,
"endpoints":{"events":"/events?client_id=<id>","health":"/health","rpc":"/rpc","schema":"/schema"}}
https://api.tinyhumans.ai/health returns OK.- Launching the executable manually with the deep link as argument:
& "C:\Users\<user>\AppData\Local\OpenHuman\OpenHuman.exe" "openhuman://auth?token=<JWT>&key=auth"
→ OpenHuman starts (or focuses if already running) but does NOT process the token. The welcome/login screen remains.
- Multiple OpenHuman processes (7+) were observed running simultaneously before being killed — likely orphaned from previous failed login attempts.
Notes
- DevTools are not accessible (Ctrl+Shift+I does nothing) and no log files were found under
%APPDATA%\OpenHuman\, so I cannot provide client-side stack traces.
- A clean reinstall + reboot did not help.
- The cloud OAuth backend is working correctly (callback succeeds, JWT is generated). The issue is purely client-side: the Windows build of v0.54.0 does not consume the
openhuman://auth?token=... deep link.
maybe I'm placed in waitlist? (UI should say this)
Happy to provide additional info or run tests.
Summary
After completing OAuth login (Google or GitHub) in the browser, the callback page at
api.tinyhumans.ai/auth/<provider>/callbackshows the "Opening OpenHuman in a few seconds..." page with anOpen OpenHumanbutton. The button triggers a deep linkopenhuman://auth?token=<JWT>&key=auth, but the OpenHuman app ignores it and stays on the welcome/login screen.Environment
Steps to reproduce
Seleziona un runtime→ choose "Esegui localmente" → continueGoogle(orGitHub) to start OAuthapi.tinyhumans.ai/auth/<provider>/callback?...and shows the "Opening OpenHuman in a few seconds..." pageOpen OpenHumanbuttonSame behavior with Google and GitHub OAuth providers.
Diagnostic data
HKCU:\Software\Classes\openhuman\shell\open\command:"C:\Users\AppData\Local\OpenHuman\OpenHuman.exe" "%1"
127.0.0.1:7788and responds with:{"api_server":"https://api.tinyhumans.ai","name":"openhuman","ok":true, "endpoints":{"events":"/events?client_id=<id>","health":"/health","rpc":"/rpc","schema":"/schema"}}https://api.tinyhumans.ai/healthreturns OK.→ OpenHuman starts (or focuses if already running) but does NOT process the token. The welcome/login screen remains.
Notes
%APPDATA%\OpenHuman\, so I cannot provide client-side stack traces.openhuman://auth?token=...deep link.maybe I'm placed in waitlist? (UI should say this)
Happy to provide additional info or run tests.