[Bug] Forced Git Bash execution on Windows breaks tool use due to missing environment variables ("command not found")

On Windows, the Alma AI client automatically detects and forces the use of Git Bash (bash.exe) to execute terminal commands and agentic tools. However, the spawned Git Bash environment fails to inherit the complete Windows system and user %PATH% environment variables. As a result, critical global tools (such as Node.js, npm, Python, and even Alma's own CLI tools) cannot be resolved, constantly throwing command not found errors and completely breaking the AI's autonomous tool-use capabilities.

Environment

• OS: Windows 11

• Alma Client Version: 0.0.797

Steps to Reproduce

1. Ensure you have globally installed tools on Windows (e.g., Node.js or Python available in PowerShell/CMD via environment variables).

2. Open the Alma desktop client on Windows.

3. Prompt the AI to perform a task that requires terminal execution (e.g., "Check my node version" or "Run a script").

4. Observe the terminal tool execution window.

Actual Behavior

Alma attempts to run the command inside Git Bash using arguments like bash -l -c. Because Git Bash filters or strips out certain Windows paths by default, it throws:

bash: node: command not found
# or
bash: alma: command not found