Detect Environment

Detect Environment

Run the probe script at session start or when command not found occurs:

bash scripts/env-probe.sh

Output

JSON object with detected tools and their paths. Example:

{
  "python": {"cmd": ".venv/bin/python", "version": "3.11.5"},
  "pip": {"cmd": ".venv/bin/pip", "version": "23.2"},
  "package_manager": "uv",
  "node": {"cmd": "/usr/bin/node", "version": "20.10.0"},
  "tsc": {"cmd": "npx tsc", "version": "5.3.2"},
  "git": {"cmd": "/usr/bin/git", "version": "2.43.0", "in_repo": true},
  "docker": {"cmd": "/usr/bin/docker", "version": "24.0.7"},
  "dart": null,
  "flutter": null,
  "cargo": null,
  "java": null
}

Usage

• Use the cmd value from output to construct commands (e.g., use .venv/bin/python not python)
• null means the tool is not installed — don't try to use it
• Re-run after installing tools, switching project directories, or activating a virtual environment
• The script always exits 0 — missing tools are reported as null, not errors