WorkBuddy currently supports Windows 10 and above, as well as macOS 12 and above. Before downloading and installing, the most important thing is to check the operating system and processor architecture: choose Mac ARM64 for Apple M series chips, Mac x64 for Intel chips; Choose Windows x64 for standard Intel or AMD computers. Choosing the wrong version or architecture often results in installation packages failing to open, exiting immediately upon startup, or failing to run properly after logging in.
First, use a table to compare the installation package
| Computer situation | Recommended version | Current precautions |
|---|---|---|
| Windows 10/11, Intel or AMD | Windows x64 | It does not support Windows 7, 8, or 8.1 |
| Windows 11, ARM chip | Not installed for now | Official FAQ currently states that ARM64 is not supported |
| Mac, M1/M2/M3/M4, etc | Mac ARM64 | Performance and compatibility are more compatible |
| Mac, Intel chips | Mac x64 | The ARM64 version cannot run on Intel Macs |
M series Macs can also run x64 versions with Rosetta, but unless there are special compatibility requirements, ARM64 should be downloaded first. If the system version is too low, you should first evaluate and upgrade the system; it is not recommended to bypass requirements with outdated installation packages of unknown sources.
How to check if installation is complete but you can't log in?
First, set the system's default browser to a browser that can open web pages normally, then reinitiate login authorization. If you do not return to WorkBuddy after authorization, check whether the browser blocks redirects, whether the client is isolated by security software, and whether the account directory has read/write permissions. Windows also needs to check whether antivirus software or enterprise security policies prevent client startup, network access, or configuration file creation.
If it still fails, open the diagnostic tool in "Help & Feedback" to recheck, save the diagnostic report and occurrence time. The report helps distinguish network, directory permissions, rendering processes, and client configuration issues; Before sharing with support, usernames, directories, and any potentially sensitive information should be masked.
Starting for the first time is the most stable way to verify it
Don't authorize the entire hard drive right away. First, create a new test workspace with only one copy file, and send tasks like "Read file name and summarize three points, without modifying the original file." After confirming that Chinese display, model call, file reading, and result saving are all normal, gradually add the real project. If the same installation package performs differently on multiple computers, prioritize comparing system versions, chipsets, default browsers, and security software rather than reinstalling repeatedly.
