TmuxSubagentCreation

Automate Claude Code subagent creation through the tmux-driven /agents TUI.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/andallen/claude-monet --skill tmuxsubagentcreation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: TmuxSubagentCreation
Source: https://github.com/andallen/claude-monet/tree/main/skills/TmuxSubagentCreation
Command: npx skills add https://github.com/andallen/claude-monet --skill tmuxsubagentcreation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables programmatic creation of Claude Code subagents by automating the interactive /agents TUI via tmux, removing the need for manual TUI interaction and enabling repeatable provisioning.

Core Features & Use Cases

  • Automated subagent creation: Use tmux to drive Claude Code's /agents workflow and generate new subagents without manual clicks.
  • Configurable provisioning: Support location choice (Project or Personal), generation method, and custom descriptions to tailor each subagent.
  • Use Case: Batch-create multiple subagents with consistent settings in CI-like workflows or onboarding scripts.

Quick Start

Use the following sequence to create a new subagent via tmux automation:

  1. Kill any existing session: tmux kill-session -t cc 2>/dev/null || true
  2. Start new detached session with Claude Code: tmux new-session -d -s cc -x 120 -y 30 'claude'
  3. Wait for startup: sleep 4
  4. Navigate to /agents: tmux send-keys -t cc '/agents' Enter sleep 2
  5. Select "Create new agent": tmux send-keys -t cc Enter sleep 2
  6. Choose Location and Creation Method as described in steps: tmux send-keys -t cc Down Enter # Select Personal sleep 2 tmux send-keys -t cc Enter sleep 2
  7. Enter Agent Description and save: DESCRIPTION="Your detailed agent description here..." tmux send-keys -t cc "$DESCRIPTION" tmux send-keys -t cc Enter sleep 15
  8. Save and exit: tmux send-keys -t cc Enter sleep 2 tmux send-keys -t cc Escape sleep 1 tmux send-keys -t cc '/exit' Enter sleep 2 tmux kill-session -t cc

Frequently Asked Questions about TmuxSubagentCreation

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

FAQPage Schema
How do I automate Claude Code subagent creation without manual TUI interaction?

You can automate Claude Code subagent creation by scripting the interactive /agents TUI through tmux. This Skill sends keystrokes to a detached tmux session to drive the menu, removing the need for manual clicks and enabling repeatable provisioning.

Can I batch provision multiple Claude Code subagents with consistent settings?

Yes, batch provisioning of multiple Claude Code subagents is possible by applying the tmux automation sequence in a loop. This allows you to generate new subagents with consistent configuration across CI-like workflows or onboarding scripts.

Do I need tmux to run automated subagent generation in Claude Code?

Yes, you need tmux to automate the subagent generation process. The workflow requires tmux, Claude Code, and a shell environment capable of executing the scripted steps to drive the interactive TUI.

How does tmux scripting drive the /agents TUI to generate a new subagent?

Tmux scripting drives the /agents TUI by starting a detached session, sending the /agents command via send-keys, and navigating menu selections like Location and Creation Method using simulated keystrokes followed by sleep delays for processing.

What configurations can I set when creating a Claude Code subagent via tmux?

You can configure the subagent location (Project or Personal), the generation method, and a custom agent description. These options are selected and entered programmatically by sending specific keystrokes to the tmux session.

Why does my tmux automation fail to create a subagent in Claude Code?

Tmux automation fails when sleep delays are too short for the TUI to render or when send-keys sequences do not match the exact menu navigation steps. Adjusting the timing or verifying the keystroke order against the /agents workflow resolves this.