Execute commands and send keys in detached tmux sessions while capturing pane output.
npx skills add https://github.com/podcodar/webapp --skill tmux-automation
Please help me install this Agent Skill. Skill: tmux-automation Source: https://github.com/podcodar/webapp/tree/main/.opencode/skills/tmux-automation Command: npx skills add https://github.com/podcodar/webapp --skill tmux-automation
This Skill solves the problem of running interactive or long-running command workflows without losing progress when your terminal disconnects or you need to orchestrate multiple steps programmatically.
Run a Django migration or a Python REPL flow that requires multiple interactive commands while capturing output for later inspection, then cleanly tear down the session when done.
Create a detached tmux session for a long-running command, wait briefly for initialization, send input commands followed by Enter as separate key arguments, capture the resulting output, and finally kill the session.
High-intent search queries and answers about installing and using this skill.
You can automate interactive CLI sessions by creating a detached tmux session and using send-keys to programmatically input commands and special keystrokes, then using capture-pane to retrieve the resulting output for verification.
To keep long-running terminal processes running after a disconnect, start them in a detached tmux session. This creates a persistent background environment that maintains process state independently of your active terminal connection.
Yes, you can capture scrollback output from a tmux session programmatically by using the tmux capture-pane command. This allows you to retrieve and verify the resulting output from automated interactive commands executed within the session.
Yes, tmux send-keys supports special key names for driving REPLs and interactive tools. It allows you to send specific keystrokes separately from the Enter key argument, ensuring reliable programmatic input for complex terminal workflows.
The best way to manage a detached tmux session lifecycle is using tmux has-session to check if a session exists before interacting, and tmux kill-session to cleanly tear down the session and its processes when the automation workflow is complete.
Yes, you can run a Python REPL flow in a specific working directory by creating a detached tmux session with an optional working directory parameter, then sending interactive commands and capturing the output before killing the session.
furedeaManage herdr terminal multiplexer workspaces, tabs, and panes via CLI commands.
X-School-AcademyCapture terminal session screen output as text, ANSI, or structured data.
zhcndocSend keystrokes and capture pane output in tmux sessions.
KunCheng-HeCoordinate terminal-based coding agents and background processes via a multiplexer interface.
