Tmux Ops
SkillDocs & knowledgeUse tmux-style session management when a task needs parallel terminal work, durable panes, or resumable long-running commands.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Tmux Ops skill
About this skill
Self-hosted AI workspace where chat becomes visual workflows, multi-agent operations, and reviewable automations. Local memory; local or cloud models
What this skill tells your AI
The instructions your AI receives, as published by aaronnat23/disp8ch in optional-skills/tmux-ops/SKILL.md and read by ahel’s review.
Use tmux-style session management when a task needs parallel terminal work, durable panes, or resumable long-running commands.
Use when
- The work benefits from multiple concurrent terminal views.
- A long-running server, watcher, or test loop should stay attached in the background.
- The user wants a reproducible terminal layout for an investigation or rollout.
Workflow
- Name the purpose of each pane or session before creating or reusing it.
- Keep one pane for the main app, one for logs, and one for validation where possible.
- Prefer idempotent commands so a pane can be recreated safely.
- Record the commands and expected signals that indicate the session is healthy.
- Tear down or hand off the session cleanly when the task ends.
Deliverable
- Session layout.
- Commands running in each pane.
- Health signals to watch.
- Cleanup or handoff notes.
Signals
- GitHub stars
- 100
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
tmux-ops- Source
- github.com/aaronnat23/disp8ch