[Bug]: Remote Link runs a stale npm/Bun ocx instead of the Desktop app's CLI on the Child and reports it as "too old" #6942

Client or integration

OpenCodex dashboard

Area

Platform (Windows / macOS / Linux)

Summary

The Home runs every Child command through REMOTE_OCX_SCRIPT (src/link/ssh-argv.ts), which uses the non-interactive SSH PATH plus ~/.bun/bin:~/.local/bin:/opt/homebrew/bin:/usr/local/bin. It never looks in ~/.opencodex-desktop/bin or the app bundle. Desktop writes its PATH block only to interactive startup files (.zshrc, .bashrc; desktop/src-tauri/src/cli_command_posix.rs), which a non-interactive SSH session does not read. Any older npm or Bun install on the Child therefore wins over the Desktop CLI.

Two cases from one rollout:

• macOS Child with OpenCodex.app 2.83.0 and a leftover Bun-global ocx whose shebang is #!/usr/bin/env node (no Node installed): the script resolves ~/.bun/bin/ocx and gets env: node: No such file or directory. env exits 127, the status the Home treats as "ocx was not found". The only fix was adding the Desktop bin directory to ~/.zshenv.
• Windows machine with OpenCodex Desktop 2.77.0 installed: Test connection and host confirmation succeed, then the dashboard says "OpenCodex on the remote computer is too old … run ocx update … opencodex 2.58.0", because an npm-global 2.58.0 shim comes first on PATH. The advice is wrong twice: ocx update would target the npm install, and a current version would not make Windows a supported Child.

Reproduction

1. On a macOS Child, install OpenCodex.app and keep an older npm/Bun-global ocx in ~/.bun/bin.
2. From the Home: ssh <child> 'sh -c '\''PATH="$PATH:$HOME/.bun/bin:$HOME/.local/bin:/opt/homebrew/bin:/usr/local/bin"; command -v ocx; ocx --version'\'''
3. Output: /Users/<user>/.bun/bin/ocx and env: node: No such file or directory. After adding ~/.opencodex-desktop/bin to ~/.zshenv, the same command prints the Desktop CLI and opencodex 2.83.0.
4. Windows: Add Child for a host with Desktop installed plus an older npm-global ocx → "too old … opencodex 2.58.0".

Expected:

• Look for Desktop CLIs (~/.opencodex-desktop/bin/ocx, /Applications/OpenCodex.app/Contents/MacOS/ocx, the deb's /usr/bin/ocx) before the generic directories, or have Desktop also publish a non-interactive PATH entry.
• When the remote is Windows (MSYS/MINGW uname, or a Windows ocx), report that Windows Children are unsupported instead of "too old".

Version

Home 2.81.0 (OpenCodex Desktop); Children 2.83.0 (macOS Desktop) and 2.77.0 (Windows Desktop). REMOTE_OCX_SCRIPT is unchanged on dev 9b6f4b2632.

Operating system

Home macOS 27 arm64; Children macOS 27 arm64 and Windows 11 x64 (OpenSSH, Git Bash default shell)

Provider and model

No response

Logs or error output

/Users/<user>/.bun/bin/ocx
env: node: No such file or directory

원격 컴퓨터의 OpenCodex가 원격 연결을 쓰기에는 오래되었습니다. 그 컴퓨터에서 ocx update를 실행해 2.66.0 이상으로 올린 뒤 다시 시도하세요. 이유: opencodex 2.58.0

Screenshots and supporting files

No response

Redacted configuration

No response

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.