Run long CLI tasks that persist through disconnects — deployments, migrations, and batch processing
tmux gives your assistant persistent terminal sessions for tasks that take minutes or hours. Deployments, database migrations, batch processing, and build pipelines continue running even if you disconnect. The assistant manages sessions, tracks progress, and notifies you on completion.
Run deployment scripts that take 10+ minutes without worrying about connection drops
Execute long-running migrations and schema changes with progress tracking
Process large datasets, run ETL pipelines, or batch operations in the background
Run build and compilation tasks that would otherwise time out in direct execution
Tell the assistant what to run — 'deploy this to staging' or 'run the database migration'. The assistant starts it in a persistent tmux session.
The assistant names sessions descriptively (e.g., 'deploy-staging-01') so you can track multiple tasks.
Ask 'how's the deployment going?' or 'status of my migration'. The assistant reads the tmux session output and reports back.
When the task completes, the assistant sends a notification with the outcome — success, failure, or output summary.
Run this deploy script and notify me when it finishes
Started in tmux session 'deploy-01'. Estimated time: 12 minutes. I'll notify you on completion.
What's the status of my migration?
Session 'migration-prod': running for 8 minutes. Currently processing table 'events' (4 of 7). Estimated 5 minutes remaining.
Run a full test suite in the background
Started in tmux session 'tests-full'. Running 342 tests across 28 files. I'll send results when complete.