You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✗ The browser could not open the account login page. (SERVICE_UNAVAILABLE)
No browser opens. Instead, a File Explorer window opens on Documents.
Root cause (likely)
The Windows binary opens the login page by running explorer.exe <url>. The binary contains the literal explorer.exe right next to the the authorization URL must stay on the skilld.dev origin check. That causes two problems:
When explorer.exe can't parse its argument as a path or URL, it opens the user's Documents folder, which is exactly what happens here. Rust's Command argument quoting doesn't match Explorer's non-standard command-line parsing, especially for URLs containing & or #.
explorer.exe returns exit code 1 even when it succeeds, so checking its exit status reports a failure every time.
Suggested fix
Open URLs with ShellExecuteW(NULL, L"open", url, …). The open and webbrowser crates already do this on Windows, as does rundll32 url.dll,FileProtocolHandler <url>.
Don't use explorer.exe to open URLs, and don't rely on its exit code.
Workaround
npx skilld auth login --no-browser prints the authorization URL so you can open it manually.
Thanks for these issues, sorry I didn't get a chance to test Windows properly in v3 yet. Please try v3.6.5, hopefully more stable now with a windows CI test.
I'll give it a go when I finish up my current build job...thanks for getting to these so quickly!
Looks like v3.6.6 failed to build, will the changes be present in v3.6.5 too?
Activity
harlan-zw commentedon Oct 7, 2026
Thanks for these issues, sorry I didn't get a chance to test Windows properly in v3 yet. Please try v3.6.5, hopefully more stable now with a windows CI test.
Mustached-Maniac commentedon Oct 7, 2026
I'll give it a go when I finish up my current build job...thanks for getting to these so quickly!
Looks like
v3.6.6failed to build, will the changes be present inv3.6.5too?Mustached-Maniac commentedon Oct 7, 2026
can confirm that
3.6.7fixes both issues! #224 and #222