v1.159.3

What's New

Fixed

• Agents silently failing to start after a reboot (tmux mode) — when the commander was launched from inside a tmux pane (e.g. pm2 started from an agent's own session, with pm2 save baking that environment into the process definition), it inherited a stale TMUX=<socket> variable. tmux takes its socket path from $TMUX when set and, unlike its default path, will not create the parent directory for it — so once a reboot wiped /tmp, every tmux new-session failed with error creating /tmp/tmux-<uid>/default while still exiting 0. The session never started, the agent's output log stayed empty, and the watchdog later misreported it as a crashed process.
• Silent tmux spawn failures — tmux's stderr is now captured instead of discarded. A failed new-session logs the real error and reports a spawn failure, instead of going silent and surfacing minutes later as a bogus agent death.

Technical Details

• TMUX/TMUX_PANE are stripped from every tmux invocation (spawn and control commands alike), so tmux computes its own socket path and creates the directory as needed, and has-session/kill-session inspect the same socket the spawn used.
• Exit code alone is not a reliable failure signal here: tmux exits 0 even when it fails to create the session.