fix(hosts): probe ~/.local/bin/codemux-remote when PATH lookup fails#44
Merged
Conversation
The "Test connection" probe used `command -v codemux-remote` over a non-interactive SSH shell, but bootstrap installs to ~/.local/bin/codemux-remote and most distros only add that dir to PATH via ~/.profile (login shells), so the probe reported NOT_INSTALLED immediately after a successful install and the UI re-showed the Install button on every subsequent press. Fall back to running $HOME/.local/bin/codemux-remote directly when the PATH lookup misses, matching the absolute-path pattern already used by ensure_remote_binary_current and the tunnel supervisor's spawn command.
Zeus-Deus
added a commit
that referenced
this pull request
May 27, 2026
- codex_adapter: route every wrapper-script `start_session` call
through a new `start_session_resilient` helper that retries
ETXTBSY ("Text file busy") from the kernel. Cause: tokio's
fork+exec inherits sibling tests' in-flight write fds in the
same test binary, and Linux's `i_writecount` check rejects the
exec until the fd drains. Pure test-infra artifact — production
spawns a pre-installed `codex` binary. 25/25 stress runs clean.
- new-workspace-dialog: widen the chip-assertion `waitFor` to 5s.
Windows CI under load stretches paste → mock → setAttachments →
commit past the default 1s; Linux/macOS resolve well under 100ms.
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
NOT_INSTALLEDimmediately after a successful install, causing the UI to re-show the Install button on every presscommand -v codemux-remoteover a non-interactive SSH shell, but bootstrap installs to~/.local/bin/codemux-remote— and most distros only put that dir on PATH via~/.profile(login shells only)\$HOME/.local/bin/codemux-remotedirectly when the PATH lookup misses; mirrors the absolute-path pattern already used byensure_remote_binary_currentand the tunnel supervisor's spawn commandVerification
build_probe_argv_falls_back_to_home_local_binlocks in BOTH the PATH lookup AND the absolute-path fallback so a future refactor can't silently drop either branchssh::probetests passcargo checkclean,tsc --noEmitclean, vitest 1766/1766 passing~/.local/bin/codemux-remoteand\$PATH=/usr/local/sbin:/usr/local/bin:/usr/bin(no~/.local/bin), the new probe script returnsCMR: {"name":"codemux-remote","protocol_version":1,"version":"0.7.1"}where the old script returnedCMR: NOT_INSTALLEDTest plan
~/.local/binIS on the non-interactive PATH still take the fast (PATH lookup) branch