subagent

Spawn pi subagents in tmux sessions for isolated parallel tasks.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/lrhodin/snorrio --skill subagent-lrhodin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent
Source: https://github.com/lrhodin/snorrio/tree/main/skills/subagent
Command: npx skills add https://github.com/lrhodin/snorrio --skill subagent-lrhodin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn pi subagents in tmux to isolate tasks like research, exploration, builds, or parallel work. Keeps your context clean by separating tasks into dedicated sessions.

Core Features & Use Cases

  • Isolated pi subagents running in tmux sessions for independent tasks
  • Ability to spawn multiple agents with a consistent naming convention and workspace isolation
  • Wait, monitor, and read outputs with a simple, reliable signaling mechanism

Quick Start

Spawn a workspace of agents using prompts and monitor completion with the subagent wait.

Frequently Asked Questions about subagent

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

FAQPage Schema
How do I run parallel AI agents in isolated tmux sessions?

You can run parallel AI agents in isolated tmux sessions by spawning pi subagents under a consistent workspace prefix. This isolates prompts and outputs, keeping your primary context clean while tasks execute concurrently.

What is the best way to isolate long-running build tasks from my main agent context?

To isolate long-running build tasks, spawn dedicated subagents in tmux. This separates the task execution and its outputs into independent sessions, preventing context pollution in your primary workspace.

How do I wait for multiple concurrent tmux subagents to finish?

You wait for concurrent tmux subagents to finish using the 'subagent wait' command. It relies on a simple tmux signaling mechanism to reliably report completion across all sessions spawned under the workspace prefix.

Do I need tmux installed to use subagents for parallel workspace isolation?

Yes, you need tmux installed. The subagent architecture requires tmux to create isolated sessions and uses tmux signaling to report task completion, operating within a per-session pi environment.

Can I monitor exploration and research tasks across multiple isolated agents?

Yes, you can monitor exploration and research tasks across isolated agents. The system manages multiple concurrent sessions with consistent naming conventions, allowing you to track and read outputs reliably.

Why does my agent context get cluttered when running concurrent tasks?

Your agent context gets cluttered because concurrent tasks share the same workspace. Using tmux subagents isolates prompts and outputs into dedicated per-session pi environments, keeping the primary context clean.