> tmux While that's technically true, AWS CloudShell (and Google's CloudShell both) are already running in tmux and thus user spawned tmux sessions need TLC

> tmux While that's technically true, AWS CloudShell (and Google's CloudShell both) are already running in tmux and thus user spawned tmux sessions need TLC [cloudshell-user@ip-10-6-64-205 ~]$ ps awx PID TTY STAT TIME COMMAND 1 ? Ssl 0:00 node /var/lib/amazon/cloudshell/entrypoint.js 26 pts/0 Ss+ 0:00 /bin/bash -c cd ~ && tmux -l -f /var/lib/amazon/cloudshell/tmux.conf new-session -A -D -s 3671b23a-900a-4bc2-b956-67995f1e1032 32 pts/0 S+ 0:00 tmux -l -f /var/lib/amazon/cloudshell/tmux.conf new-session -A -D -s 3671b23a-900a-4bc2-b956-67995f1e1032 34 ? Ss 0:00 tmux -l -f /var/lib/amazon/cloudshell/tmux.conf new-session -A -D -s 3671b23a-900a-4bc2-b956-67995f1e1032 [cloudshell-user@ip-10-6-64-205 ~]$ tmux new -s mine sessions should be nested with care, unset $TMUX to force