Skip to content

Banner when mux auto-start binary is missing (#407) - #432

Draft
jvanderen1 wants to merge 2 commits into
kitknox:mainfrom
jvanderen1:feature/407-3-mux-missing-binary
Draft

jvanderen1 wants to merge 2 commits into
kitknox:mainfrom
jvanderen1:feature/407-3-mux-missing-binary

Conversation

@jvanderen1

@jvanderen1 jvanderen1 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • When mux auto-start cannot find tmux / herdr / zmx on the remote, print a clear fallback and show an in-app banner
  • Drop the optimistic mux binding so the pane is not treated as still attached
  • Detects the rootshell fallback marker/OSC and common shell “not found” lines

Depends on #430 (reuses the detach banner). Part of #407.

Optional. Not required to land detach/resume (#430) or tmux close-after-reattach (#431). Safe to leave as draft until someone wants the missing-binary path.

Test plan

  • Profile with tmux auto-start on a host without tmux → banner, normal shell, no mux chrome
  • Same for zmx / herdr
  • Host that has the binary is unchanged

@jvanderen1
jvanderen1 force-pushed the feature/407-3-mux-missing-binary branch 2 times, most recently from a74322c to 01d6ab4 Compare September 13, 2026 21:20
Leave a mux session running from Tabs / the tab menu, focus a live
auto-start attachment instead of opening a second client, and offer
Reconnect on a short banner. Raw-pane chords use swipe discovery
when present, otherwise the usual defaults.
Detect the remote fallback marker/OSC (and common “not found” lines)
and show the same style of banner as detach, without pretending the
pane is still that multiplexer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant