Global AI not found - Freecad 1.1

[skyfirexii]

Install doesn't find Freecad 1.1 on Windows 11:

Copying the module manually results in registration but Freecad reports:
Event observer module: No module named "Pyside2"

Switching to the AI Copilot workbench then reports:
Global AI service not found
Cannot find icon: AICopilot.svg

[mgergo76]

Same here. Installation has problem.

Did all the steps according to Readme but does not recognized program parts (no FreeCAD, Claude found).

[markspotsthex]

I am using a MacBook M4 Pro with Tahoe 26.5.1. I have the same experience as the first user.

[FlatterAtMainz]

Two separate bugs bundled in this report:

1. "Event observer module: No module named 'Pyside2'" — fixed in Fix event observer failing to import on FreeCAD 1.1+ (no PySide2) #12. event_observer.py imported PySide2 directly, but FreeCAD 1.1+ ships PySide6 only. Switched to FreeCAD's own PySide compatibility shim.

2. "Global AI service not found" — fixed in Fix "Global AI service not found" false warning (Python name mangling) #15. This one's a genuine Python bug, not a packaging/environment issue: GlobalAIService.start() sets FreeCAD.__ai_global_service = self from inside its own class body, which Python name-mangles to FreeCAD._GlobalAIService__ai_global_service. AICopilotWorkbench's status check reads hasattr(FreeCAD, '__ai_global_service') from a different class, which mangles to a completely different attribute name — so the check was structurally guaranteed to always fail and print "not found," regardless of whether the service was actually running. Fix "Global AI service not found" false warning (Python name mangling) #15 renames these to single-underscore names, which Python doesn't mangle, so every reader/writer now agrees on the same attribute.

("Cannot find icon: AICopilot.svg" is a separate missing-resource issue, not covered by either fix — likely a packaging gap where the icon file isn't included/found in some installs.)

Not able to speak to the Windows-specific "no FreeCAD, Claude found" detection issue mentioned in the comments here — that may be worth splitting into its own issue if it's still occurring, since it sounds like checkFreeCadInstallation()'s Windows path detection rather than either of the two bugs above.