Run long-running development commands in isolated tmux panes.
npx skills add https://github.com/roerohan/skills --skill tmux-roerohan
Please help me install this Agent Skill. Skill: tmux Source: https://github.com/roerohan/skills/tree/main/tmux Command: npx skills add https://github.com/roerohan/skills --skill tmux-roerohan
This Skill solves the common issue of AI agents running long-running development commands (such as dev servers, file watchers, database consoles, and log tailing) directly in the OpenCode shell, which clutters the terminal, loses output when sessions end, and makes it difficult to manage multiple concurrent processes.
Use the tmux skill to start your web development server in a named tmux pane so you can monitor its logs and send input to it without blocking your OpenCode terminal.
High-intent search queries and answers about installing and using this skill.
You can manage multiple dev servers by running them in isolated, named tmux panes to keep your terminal clean and preserve process output. A registry tracks pane metadata to avoid duplicate processes and enable reliable service restarts.
You can monitor logs from long-running processes using helper scripts that capture output from named tmux panes. This allows you to read logs and send input to any service without switching terminal contexts or losing session history.
The best way to run fullstack workflows is by executing each concurrent service, such as web servers and background workers, in its own named tmux pane. Helper scripts arrange panes side-by-side and handle graceful shutdown for all processes.
Yes, you need both tmux and lsof installed to manage background dev commands. Tmux provides the isolated panes for running processes, while lsof helps check service readiness and manage port usage.
Yes, you can reuse an existing running pane because the Skill maintains a local registry of managed panes. This registry tracks metadata to avoid duplicate processes and allows you to reliably interact with or restart services already running.
You can gracefully shut down concurrent dev servers using pre-built helper scripts designed for pane shutdown. These scripts manage the termination of services across your tmux session while relying on the pane registry for tracking.
Kastalien-ResearchSend keystrokes to tmux panes and scrape their output.
191854169Send keystrokes and capture pane output in tmux sessions.
matparangAutomate tmux sessions by sending keystrokes and capturing pane output.
furedeaManage herdr terminal multiplexer workspaces, tabs, and panes via CLI commands.
