Manage persistent tmux sessions for long-running background processes.
npx skills add https://github.com/roach88/claude-config --skill subagent-roach88
Please help me install this Agent Skill. Skill: subagent Source: https://github.com/roach88/claude-config/tree/main/skills/subagent Command: npx skills add https://github.com/roach88/claude-config --skill subagent-roach88
This skill solves the problem of losing state for long-running background processes like builds, log monitoring, and test runs when the AI context window resets, by using persistent tmux sessions that continue running independently of the AI's context.
Use the subagent skill to create a persistent tmux session named cc-build-watch that runs the command npm run build --watch to continuously monitor your project's build process in the background.
High-intent search queries and answers about installing and using this skill.
You can keep background processes running during AI context window resets by using persistent tmux sessions that operate independently of the AI context, ensuring continuous execution of long-running tasks like build watches or log tailing without manual restarts.
To monitor a build process in the background using tmux, create a persistent session with a standardized naming prefix, send your build command to it, and read the output stream later to check the status without interrupting the process.
Yes, you can run continuous log tailing without losing state by attaching the log command to a persistent tmux session, which maintains the process state and output history independently of the AI session lifecycle.
Persistent session management includes safety guardrails that require explicit approval before killing tmux sessions, preventing unauthorized termination of active background processes like test runs or build monitoring tasks.
The best way to manage multiple background tasks without naming conflicts is using a standardized naming prefix for all tmux sessions, which ensures organized creation, listing, and safe termination of each persistent process.
Reading tmux session output before sending new commands prevents errors by allowing you to verify the current state of the background process, ensuring you do not interrupt an ongoing build or test run with conflicting input.
knoopxAutomate tmux session multiplexing and background task orchestration via CLI commands.
WrongStackParse WrongStack session JSONL logs and generate structured markdown audit reports.
RepairYourTechManage long-lived processes in tmux sessions with structured windows.
cbooneCreate a git worktree and tmux window with an injected task prompt.
