tmux-status
Show status of all tmux sessions including dev environments, spawned agents, and running processes
Best use case
tmux-status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Show status of all tmux sessions including dev environments, spawned agents, and running processes
Teams using tmux-status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tmux-status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tmux-status Compares
| Feature / Agent | tmux-status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Show status of all tmux sessions including dev environments, spawned agents, and running processes
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /tmux-status - Overview of All tmux Sessions
Show status of all tmux sessions including dev environments, spawned agents, and running processes.
## Usage
```bash
/tmux-status # Compact overview
/tmux-status --detailed # Full report with metadata
/tmux-status --json # JSON export
```
## Process
Invokes the `tmux-monitor` skill to discover and report on all active tmux sessions.
```bash
# Get path to monitor script
MONITOR_SCRIPT=".claude/skills/tmux-monitor/scripts/monitor.sh"
[ ! -f "$MONITOR_SCRIPT" ] && echo "❌ tmux-monitor skill not found at $MONITOR_SCRIPT" && exit 1
# Determine output mode
OUTPUT_MODE="compact"
[[ "$1" == "--detailed" ]] || [[ "$1" == "-d" ]] && OUTPUT_MODE="detailed"
[[ "$1" == "--json" ]] || [[ "$1" == "-j" ]] && OUTPUT_MODE="json"
# Execute monitor script
bash "$MONITOR_SCRIPT" "$OUTPUT_MODE"
```
## Output Modes
### Compact (Default)
Quick overview:
```
5 active sessions:
- dev-myapp-1705161234 (fullstack, 4 windows, active)
- dev-api-service-1705159000 (backend-only, 4 windows, detached)
- agent-1705160000 (codex, running)
- agent-1705161000 (aider, completed ✓)
- claude-work (main session, current)
3 running servers on ports: 8432,3891,5160
Use /tmux-status --detailed for full report
```
### Detailed
Full report with metadata, services, ports, and recommendations.
### JSON
Programmatic output:
```json
{
"sessions": [
{
"name": "dev-myapp-1705161234",
"type": "dev-environment",
"windows": 4,
"panes": 8,
"attached": true
}
],
"summary": {
"total_sessions": 5,
"total_windows": 12,
"total_panes": 28
}
}
```
## Contextual Recommendations
After displaying status, provide recommendations based on findings:
**Completed agents**:
```
⚠️ Found completed agent sessions
Recommendation: Review and clean up: tmux kill-session -t <agent-session>
```
**Long-running detached sessions**:
```
💡 Found dev sessions running >2 hours
Recommendation: Check if still needed: tmux attach -t <session-name>
```
**Many sessions (>5)**:
```
🧹 Found 5+ active sessions
Recommendation: Review and clean up unused sessions
```
## Use Cases
### Before Starting New Environment
```bash
/tmux-status
# Check for port conflicts and existing sessions before /start-local
```
### Monitor Agent Progress
```bash
/tmux-status
# See status of spawned agents (running, completed, etc.)
```
### Session Discovery
```bash
/tmux-status --detailed
# Find specific session by project name or port
```
## Notes
- Read-only, never modifies sessions
- Uses tmux-monitor skill for discovery
- Integrates with tmuxwatch if available
- Detects metadata from `.tmux-dev-session.json` and `{{HOME_TOOL_DIR}}/agents/*.json`Related Skills
tmux-monitor
Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.
tmux-message
Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — "claude-peers fallback", "tmux send-keys", "send to peer via tmux", "inject directive", "deliver to nanoclaw/hermes peer", "peer message". Tmux-only — won't reach peers running outside tmux.
swarm-status
Display comprehensive status dashboard for a swarm team
reflect-status
Show reflection metrics, pending reviews, sidecar coverage, and GraphRAG health. Read-only views into the reflect system state. Can also approve/reject pending low-confidence items.
tmux-verify
The outer "is this TUI feature ACTUALLY done?" proof loop for the ainb terminal app. Use when the user asks to "verify the TUI is actually done", "prove this TUI feature works", "validate per tmux-verify", "vhs verify each journey", "frame-truth check the UI", "is the diff actually shown correctly", or to define the acceptance contract for a TUI goal. Orchestrates 6 gates — (1) comprehensive tmux-ui-tripwire passes, (2) a vhs recording per user journey whose frames are READ with /media-processing to assert the EXACT user-visible outcome (not "screen shows something"), (3) one recording per journey, (4) fix-loop until acceptance + tripwire green, (5) a continuous /explain-to-me explainer (tests + commits + GIFs) hosted on /here-now, (6) final HTML-solid validation with the human as the last gate. References (does not reimplement) tmux-ui-tripwire, /media-processing, /explain-to-me, /here-now.
tmux-ui-tripwire
Write or debug tmux-driven end-to-end TUI tests ("tripwires") for the ainb terminal app. Use when the user asks to "write a tmux test", "add a tripwire", "verify the TUI in tmux", "test feature X by pressing key Y", "validate plugin Z renders", or when editing any file under `crates/ainb-core/tests/tripwire_*.rs`. Codifies the silent traps we hit during Phase 7 plugin testing — macOS AMFI SIGKILL of staged binaries (exit 137, no stderr), first-run wizard intercepting keystrokes, EnvFilter crate-name drift hiding logs, and substring-OR assertions that pass while the feature is broken. Use proactively before writing any new `tripwire_*.rs` test, and reference whenever an existing tripwire fails for non-obvious reasons.
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design
token-usage
Show Claude Code token usage across sessions — daily, weekly, per-project, and per-session breakdowns. Parses {{HOME_TOOL_DIR}}/projects/**/*.jsonl for consumption data. Use when the user asks about token usage, costs, how many tokens were used, session statistics, or wants a usage report.