spawn

Spawn a new tmux window and execute a prompt without prior context.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/shuu5/twill --skill spawn-shuu5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn
Source: https://github.com/shuu5/twill/tree/main/plugins/session/skills/spawn
Command: npx skills add https://github.com/shuu5/twill --skill spawn-shuu5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn a new tmux window and execute a specified prompt without inheriting prior conversation context.

Core Features & Use Cases

  • Create an independent session in a new tmux window and run a given prompt.
  • Optionally use --worktree to create a separate git worktree for isolated sessions.
  • Do not carry over conversation context; supports window naming, project navigation, and prompt injection.

Quick Start

Spawn a new cld session in a tmux window and execute your prompt immediately, optionally creating a separate worktree with --worktree.

Frequently Asked Questions about spawn

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

FAQPage Schema
How do I run a prompt in a new tmux window without inheriting previous conversation context?

You can spawn a new tmux session that executes your prompt immediately in an isolated window, ensuring no previous conversation context is carried over into the new task.

How do I isolate git work in a separate directory using a worktree and tmux?

You can isolate git work by using the worktree mode to create a separate git worktree directory, then spawning a fresh tmux window that operates within that isolated worktree for your specific prompt.

Can I specify a custom tmux window name when spawning a new session for a prompt?

Yes, you can specify a particular window name when you spawn a new tmux session. The intention detection mechanism assigns that custom name to the fresh window before injecting your prompt.

What happens if spawning a tmux session or worktree fails during prompt execution?

If the session spawn or worktree creation fails, the process triggers an automatic rollback. This cleans up incomplete session artifacts and safely aborts the prompt injection to prevent partial state.

Does this approach support watching for background task completion in tmux?

Yes, after injecting the prompt into a waiting tmux session, you can optionally enable a watch for completion. This monitors the background task and reports back when the isolated prompt finishes executing.