spawn

Spawn parallel Amp agents in tmux windows with thread linkage.

5|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill spawn-humblemuzzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/spawn
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill spawn-humblemuzzu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, amp, bash, coreutils, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Spawn independent Amp agents to handle side-quests in parallel without interfering with main tasks.

Core Features & Use Cases

  • Spawn separate Amp agents in individual tmux windows, each linked to a parent task to maintain context.
  • Enable coordinated workflows with handoffs and thread linkage for parallel exploration of different sources.
  • Use case: during a long coding session, spawn multiple agents to investigate distinct subproblems and report findings back to the main thread.

Quick Start

Run scripts/spawn-amp "<task description>" to launch a new independent Amp agent in a tmux window and link it to the parent thread.

Frequently Asked Questions about spawn

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

FAQPage Schema
How do I spawn parallel AI agents in tmux windows?

To spawn parallel AI agents in tmux windows, run the spawn-amp script with a task description. This creates an independent Amp agent in a new tmux window and links it to the parent thread for context.

Can I run multiple Amp agents for side-quests without interfering with my main task?

Yes, you can run multiple Amp agents for side-quests without interfering with your main task. The skill spawns each agent in an independent tmux window, preventing duplicated effort and conflicting findings during concurrent exploration.

How do I link spawned agents back to a parent task's context?

To link spawned agents back to a parent task's context, the skill automatically wires each new Amp agent to its parent thread during creation. This maintains context and enables coordinated workflows with seamless handoffs.

Do I need tmux installed to spawn independent Amp agents?

Yes, you need tmux installed to spawn independent Amp agents. The skill depends on tmux, amp, bash, and coreutils to create separate windows for each agent and manage the parallel execution environment.

What is the best way to investigate distinct subproblems concurrently during a coding session?

The best way to investigate distinct subproblems concurrently during a coding session is spawning separate Amp agents. Each agent explores different sources in individual tmux windows and reports findings back to the main thread.

Are there limitations when using parallel agents for concurrent exploration?

A limitation of using parallel agents for concurrent exploration is that spawned agents operate independently in separate tmux windows. Users must manage handoffs manually if tasks become interdependent rather than remaining isolated side-quests.