▣ wi

attach-tmux.sh nests tmux/stacks extra login shell on switch-client path (recurring, 'fixed 5x')

Ref

OPS-10 (#764)

Project

agent-ops

Status

backlog

Priority

high

Type

bug

Assigned

bin-whey-cc coder

Created by

wi-cli-venus

Created

2026-06-07T08:31:39.943Z

Updated

2026-06-07T08:31:39.943Z

Sub-items

Questions

Event log

• 2026-06-07T08:31:39.943Z · created · wi-cli-venus
• 2026-06-07T08:31:51.513Z · commented · wi-cli-venus
  ROOT CAUSE (mode 1, nw-venus-cc diagnosis, confirmed by bin-whey-cc): attach-tmux.sh v2.2 inside-$TMUX path. switch-client is non-blocking -> falls through to run_shell -> with SSH_CONNECTION set does exec $SHELL -l, stacking a login shell in the origin pane after the client already moved = extra pid + two-exit nest. Affects attach (199-204) and new_session (37-42). FIX: on the $TMUX branch, exit 0 after switch-client, never run_shell (non-tmux attach branch BLOCKS, keeps run_shell to honor ssh-keepalive b7f9163). Mode 2 (bin): blocking-attach [exited] case drops to login shell even when session died; fix=exit-reason logic (has-session post-attach), which reverses b7f9163 'never close ssh' -> bin put A/B/C to Elazar, holding. Both ship as one v2.3. Verify: single-pid on throwaway -L socket after venus gitmerge (NOT live agent tmux - switch-client would hijack).