gobdovan nailed it. The CLI is a drop-in for existing tmux workflows; the SDK eases your flow when you'd otherwise be writing brittle send-keys + sleep + capture loop. But that's just one one of the use cases. rmux should be used to make beautiful TUI, something very dirty to do with tmux. Especially the day you want to do integration testing (playwright style)
And what are you automating regarding your tmux sessions exactly actually? I use tmux daily, but I never feel the need to do any automation of managing my tmux panes.
Comments
It's not clear to me what this does that tmux doesn't? Agents can already interact with tmux, so what does this provide?
tmux send-keys -t a 'npm test' Enter
sleep 2
tmux capture-pane -p -t a ```
``` pane.send_text("npm test\n").await?;pane.wait_for_text("Tests passed").await?;
let snapshot = pane.snapshot().await?; ```
gobdovan nailed it. The CLI is a drop-in for existing tmux workflows; the SDK eases your flow when you'd otherwise be writing brittle send-keys + sleep + capture loop. But that's just one one of the use cases. rmux should be used to make beautiful TUI, something very dirty to do with tmux. Especially the day you want to do integration testing (playwright style)
And what are you automating regarding your tmux sessions exactly actually? I use tmux daily, but I never feel the need to do any automation of managing my tmux panes.