tabs
/tabs
Use when the user asks to "list my claude sessions", "which windows are waiting", "/ar:tabs". Discovers Claude sessions across tmux windows and reports which need attention.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when the user asks to "list my claude sessions", "which windows are waiting", "/ar:tabs". Discovers Claude sessions across tmux windows and reports which need attention.
Triggers from the description
Arguments
/tabs [A,B:command] or [all:continue] or [awaiting:status]
Original author description
Use when the user asks to "list my claude sessions", "which windows are waiting", "/ar:tabs". Discovers Claude sessions across tmux windows and reports which need attention.
How it works
- Context
- Your Task
- Workflow
- Discovery
- User Selection Syntax
- Execution
- Prompt Types
- Session Table Format
SKILL.md preview
---
name: tabs
description: Use when the user asks to "list my claude sessions", "which windows are waiting", "/ar:tabs". Discovers Claude sessions across tmux windows and reports which need attention.
allowed-tools: Bash(tmux *), Bash(uv *)
argument-hint: "[A,B:command] or [all:continue] or [awaiting:status]"
---
# Claude Session Manager
<purpose>
Discover, analyze, and interact with Claude Code sessions across tmux windows.
## Context
Current tmux sessions and Claude windows:
Run `tmux list-sessions` and read its output before choosing a session.
## Your Task
The user's request is the task description for everything below.
If no arguments provided, discover all Claude sessions and present them to the user.
</purpose>
<workflow>
## Workflow
1. **Discover** - Run the discovery script to get session data
2. **Present** - Show sessions as table with letter labels (A, B, C...)
3. **Ask** - Get user selection for which sessions to interact with
4. **Execute** - Run commands on selected sessions
## Discovery
```bash
"${CLAUDE_PLUGIN_ROOT}/commands/tabs-exec"
```
## User Selection Syntax
| Syntax | Meaning |
|--------|---------|
| `A,C` or `AC` | Select sessions A and C |
| `A:git status` | Run custom command on session A |
| `B:pwd, C:git log` | Different commands per session |
| `all:continue` | Execute on all discovered sessions |
| `awaiting:continue` | Execute only on sessions awaiting input |
## Execution
After user confirms, execute via:
```bash
# Using tabs-exec
# NOTE: --execute requires the full session JSON from discovery phase, not a minimal stub.
# Claude should pass the full session data obtained from the discovery run above.
echo '{"selections": "B,C", "command": "continue", "sessions": [...session_data_from_discovery...]}' | "${CLAUDE_PLUGIN_ROOT}/commands/tabs-exec" --execute
# Direct tmux (for simple commands)
tmux send-keys -t "session:window" "command"
tmux send-keys -t "session:window" C-m # Enter as a separate call, as tmux-automation requires
```
## Prompt Types
When discovering sessions, detect what state each Claude session is in:
| Type | Visual Indicator |
|------|------------------|
| `input` | Standalone `>` prompt - ready for input |
| `plan_approval` | "Would you like to proceed?" |
| `tool_permission` | `[Y/n]` or numbered options `[1] [2]` |
| `question` | Multi-choice with ❯ selector |
| `clarification` | Question ending with `?` |
| `working` | No prompt detected - Claude is active |
</workflow>
<output_contract>
## Session Table Format
Present discovered sessions as:
```
| # | Session | Purpose | Status |
|---|---------|---------|--------|
| A | main:3 | Feature dev | awaiting input |
| B | main:5 | Testing | working |
| C | work:1 | Bug fix | plan approval |
```
Then ask: "Which sessions would you like to interact with?"
**Related**:
- `agents/tmux-session-automation.md` (agent `ar:tmux-session-automation`) - Advanced session lifecycle automation
- `agents/cli-test-automation.md` (agent `ar:cli-test-automation`) - CLI testing automation patterns
**Implementation**: See `tabs-exec` script for discovery and execution logic.
</output_contract>
Versions
The database has no other skills named tabs.
Database snapshot: 13.11.2026 · package version 8c63c717257b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100tabw
Use when the user asks to "continue every session", "send this to all windows", "/ar:tabw". Acts on Claude sessions across tmux windows; destructive to in-flight work, so it states what it will do before doing it. - 90waiting-on-me
Sweep all recent Claude Code sessions for ones waiting on the user. Use when the user says "sweep my sessions", "what is waiting on me", "which sessions need me", "scan my sessions", or asks to collect open questions across sessions and answer them. Finds sessions that ended on… - 100tmux-fleet
Run several coding agents in parallel in tmux windows, each under its own clausona profile (another Claude Code or Codex account, or an API model such as GLM or DeepSeek), then watch them, check their work and retire them. Use when the user works in tmux, on their own machine or… - 100stowdeck
Open Stowdeck and use it to list running or recent Claude Code sessions, list saved snapshots, and save a snapshot of the running sessions with an optional note (Windows). Use when the user asks to open or show Stowdeck; list, show or check their running, open or active Claude… - 91orchestrate
Orchestrate one natural-language goal into parallel tmux Claude Code sessions. It decomposes the goal (with your approval), plans each task with wiki-plan, implements and reviews, runs an integration test, and merges after your confirmation. Use to build a goal across multiple… - 100tmux-agent-lane-orchestrator
Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries. Use when multiple coding-agent workers run in tmux windows named L1, L2, and similar lane identifiers.