Telegram bridge fails with "openshell: not found" because ~/.local/bin isn't on PATH for child processes

[ksimback]

Environment

• Ubuntu 24 on DigitalOcean
• OpenShell v0.0.6 (installed to ~/.local/bin/openshell)
• NemoClaw from main (March 17, 2026)

Problem

OpenShell installs to ~/.local/bin/, which is available in interactive bash sessions via .bashrc but not to child processes spawned by the Telegram bridge via /bin/sh. The bridge calls execSync("openshell sandbox ssh-config ...") which fails with:

/bin/sh: 1: openshell: not found

Workaround

Create a symlink: ln -s ~/.local/bin/openshell /usr/local/bin/openshell

Expected behavior

Either install.sh should install/symlink openshell to a system-wide path, or the bridge should resolve the openshell binary path explicitly rather than relying on PATH.

[brianwtaylor]

PR #222 also adds resolveOpenshell() to locate the binary when ~/.local/bin isn't on PATH for child processes launched via nohup/systemd.