Browser Hand: Python 3 detection shows ✗ even when python3 is installed

[f-liva]

Description

In the Browser Hand activation page, the Python 3 requirement check shows ✗ Python 3 must be installed even though python3 is already installed in the system.

Running apt install python3 from inside the container confirms it's already installed:

root@cloud:/# sudo apt install python3
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3 is already the newest version (3.11.2-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Contradictory UI Messages

After clicking through the installation steps, the dashboard shows contradictory messages:

• ✓ Installation complete!
• ✓ python3 — Python 3 must be installed installed successfully
• ✓ playwright — Playwright must be installed is already available

So it detects python3 and playwright as available, but the initial check still shows ✗.

Expected Behavior

The Python 3 requirement check should detect that python3 is already installed and show ✓ from the start, without requiring the user to go through the installation steps.

Environment

• OpenFang v0.3.26 running in Docker (debian:bookworm-slim)
• python3 installed via apt
• playwright installed via pip3
• Chromium installed via playwright install --with-deps chromium

[technerd-official]

had the same problem. create a sym link in usr/bin and point python3.12 to python

[f-liva]

Update: The detection issue is caused by the check looking for python instead of python3. Creating a symlink resolves it:

ln -s /usr/bin/python3 /usr/bin/python

After this, the Browser Hand correctly shows ✓ for Python 3. The detection logic should check for python3 first (which is the standard binary name on Debian/Ubuntu), not just python.

[f-liva]

Additional issue: After activating the Browser Hand, the Hands page still shows the "Activate" button instead of reflecting that it's already active. The UI doesn't update to show the current enabled state.