Any agent write tool call to the workspace returns the above error.

TL;DR

The most likely fix is to modify the moltbot-sandbox-fs bridge script to use the absolute path to the python3 executable.

Guidance

• Verify the python3 executable path is correctly set to /usr/bin/python3 in the system configuration.
• Update the moltbot-sandbox-fs bridge script to use the absolute path /usr/bin/python3 instead of relying on the system PATH.
• Check the shell context in which the moltbot-sandbox-fs bridge script is running to ensure it has the necessary environment variables set.
• Consider setting the PATH environment variable explicitly in the script or the container configuration to include /usr/bin.

Example

# Example of updating the script to use the absolute path
/usr/bin/python3 script.py

Notes

The solution assumes that the python3 executable is indeed installed at /usr/bin/python3 and that the issue is solely due to the PATH not being inherited by the shell context in which the script runs.

Recommendation

Apply workaround: Update the moltbot-sandbox-fs bridge script to use the absolute path to the python3 executable, as this directly addresses the error message indicating that python3 cannot be found.