Bug Description
The Factory AI Desktop App is unable to detect or connect to the local daemon if the Windows user profile path contains non-ASCII characters (e.g., the Polish letter "ł" in C:\Users\Mikołaj). While the CLI daemon runs and authenticates perfectly, the Desktop GUI fails to parse the path, resulting in encoding corruption (``) and a subsequent daemon crash.
Steps to reproduce
- Start and authenticate a local daemon session via CLI (droid) on a Windows machine where the user directory contains a non-ASCII character.
- Open the Factory AI Desktop App.
- Check the connection status to the local machine.
Expected behavior
The Desktop App should properly support UTF-8 encoding for Windows paths. It should accurately resolve the user directory containing non-ASCII characters, successfully connect to the active local daemon, and maintain a stable session without causing path corruption or process crashes.
Actual behavior
The Desktop App completely fails to detect the local machine and the active CLI session. The underlying daemon crashes automatically because it tries to perform operations on a corrupted path string (C:\Users\Miko<?>aj).
Environment
- OS: Windows 11 / win32 (Version 10.0.26200)
- App Version: 0.107.1
- Electron Version: 39.2.7
- Component: Factory Desktop App
Bug Description
The Factory AI Desktop App is unable to detect or connect to the local daemon if the Windows user profile path contains non-ASCII characters (e.g., the Polish letter "ł" in C:\Users\Mikołaj). While the CLI daemon runs and authenticates perfectly, the Desktop GUI fails to parse the path, resulting in encoding corruption (``) and a subsequent daemon crash.
Steps to reproduce
Expected behavior
The Desktop App should properly support UTF-8 encoding for Windows paths. It should accurately resolve the user directory containing non-ASCII characters, successfully connect to the active local daemon, and maintain a stable session without causing path corruption or process crashes.
Actual behavior
The Desktop App completely fails to detect the local machine and the active CLI session. The underlying daemon crashes automatically because it tries to perform operations on a corrupted path string (C:\Users\Miko<?>aj).
Environment