tmux-claude-session-spawner

Name: tmux-claude-session-spawner
Availability: InStock
Author: tankygranny05

Spawn and rename tmux sessions for Claude Code instances.

2|Updated Jan 30, 2026

Search Tags:#automation #developer tools #claude #process management #session management #tmux

Ready to run

npx skills add https://github.com/tankygranny05/agent-box --skill tmux-claude-session-spawner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tmux-claude-session-spawner
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/seed/codex-skills/tmux-claude-session-spawner
Command: npx skills add https://github.com/tankygranny05/agent-box --skill tmux-claude-session-spawner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill streamlines the process of launching and managing multiple tmux sessions for Claude Code, ensuring they are reliably named and identifiable for efficient workflow management.

Core Features & Use Cases

Batch Session Spawning: Launch multiple Claude Code instances in tmux, respecting system limits.
Automatic Renaming: Sessions are automatically renamed to include Claude's session ID (sid) and process ID (pid) for easy tracking.
Use Case: When working on multiple parallel tasks requiring Claude Code, spawn and manage them all within tmux, with each session clearly labeled by its unique identifiers for quick access and debugging.

Quick Start

Use the tmux-claude-session-spawner skill to spawn and rename 5 Claude Code tmux sessions.

Frequently Asked Questions about tmux-claude-session-spawner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage multiple Claude Code tmux sessions in parallel?▼

Batch spawning launches multiple Claude Code instances in tmux while respecting system limits, automatically renaming each session to include its Claude session ID and process ID for reliable tracking and access.

Why does macOS terminal device exhaustion happen when running Claude Code?▼

macOS terminal device exhaustion occurs when spawning too many concurrent processes exceeds system limits. Batching tmux session creation and performing automated cleanup by session name prefix prevents this exhaustion.

How do I automatically rename tmux sessions with Claude process IDs?▼

Automatic renaming detects the active Claude session ID and process ID, then applies a standardized naming format to the tmux session for easy identification and debugging.

Can I clean up Claude tmux sessions automatically by name prefix?▼

Yes, you can clean up Claude tmux sessions automatically by targeting a specific session name prefix, removing only spawned Claude Code instances while preserving other active tmux sessions.

What is the best way to track parallel Claude Code instances for debugging?▼

Tracking parallel Claude Code instances is best achieved by spawning them in tmux and using standardized session names that embed the unique Claude session ID and process ID for quick access and debugging.