Two problems made the auto-attach loop:
$TMUX was the only nesting guard, and it is trivially lost - sudo -i,
env -i, ssh, and dropbear all hand back an interactive tty shell with it
unset, so a shell below tmux would start another tmux. The guard also
never checked for a login shell, so anything spawning `$SHELL -i`
(fzf-tmux, file-manager shell escapes, editor :sh) dragged in a whole
tmux client and a fresh grouped session. Now guarded on a login shell
with stdin and stdout both a terminal, a $TERM that can host tmux, and
an exported $TMUX_AUTOSTART that survives into panes and into nested
shells that strip $TMUX.
detach-on-destroy was off while the per-client sessions set
destroy-unattached on. Those fight: detaching destroys the session, and
off means the client is then switched to the most recently active
remaining session instead of being allowed to leave - so detach put you
back into "main". Restored to on, which is also the default.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Guarded to only fire for interactive shells with a real tty, when
tmux isn't already active, and only if the tmux binary is found -
so it falls back to a plain shell if any of that isn't true. Not
exec'd, so an unexpected tmux exit also drops back to a normal shell
instead of closing the connection. Replaces manually running bin/tmx.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Same host-differentiation as the tmux statusbar: blue accent for
prosrvdemadev01, existing yellow/gray colors kept as the default
elsewhere.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adds a blue accent for prosrvdemadev01 in the status bar (hostname
and selected window name), keeping the existing color as the default
for all other hosts, via tmux's native host_short format conditional.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
daniel fusseranddafu