wt-session-manager

Coordinate hub and worker Claude sessions for bead-driven development.

2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/badri/wt --skill wt-session-manager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wt-session-manager
Source: https://github.com/badri/wt/tree/main/examples/claude-code-skill
Command: npx skills add https://github.com/badri/wt --skill wt-session-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables Claude to orchestrate bead-driven development by managing a hub session and multiple worker sessions across projects.

Core Features & Use Cases

  • Hub orchestration: spawn, monitor, and clean up parallel Claude-driven worker sessions from a single hub.
  • Multi-project readiness: aggregate ready beads across registered projects and route work efficiently.
  • Lifecycle guidance: provide prompts, switch context, and manage handoffs to preserve context across restarts.
  • Reference-guided commands: consult the included references for detailed CLI usage and workflows.

Quick Start

Start a hub with wt hub, inspect ready beads with wt ready, spawn workers with wt new <bead>, monitor with wt watch, and close sessions with wt close <name>.

Frequently Asked Questions about wt-session-manager

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

FAQPage Schema
How do I orchestrate parallel Claude sessions across multiple projects?▼

You can orchestrate parallel Claude sessions by using a hub to spawn, monitor, and clean up worker sessions. This approach automates coordination by scheduling workers for ready beads and aggregating results across projects.

What is bead-driven development and how does a session hub manage it?▼

Bead-driven development organizes work into discrete beads processed by Claude. A session hub manages this by scheduling, spawning, and monitoring parallel worker sessions for ready beads, then tracking progress and cleaning up resources.

How do I start a hub and spawn workers for ready beads?▼

Start a hub using the wt hub command, inspect ready beads with wt ready, and spawn workers with wt new <bead>. You can monitor active workers with wt watch and close sessions using wt close <name>.

Can I preserve context for Claude workers across session restarts?▼

Yes, you can preserve context across restarts through lifecycle guidance. The hub manages handoffs, provides prompts, and switches context to maintain state for Claude-driven worker sessions during bead processing.

Do I need any specific CLI tools to manage bead-driven workflows?▼

You need the wt CLI to manage bead-driven workflows. The Skill leverages wt commands to spawn hubs, inspect ready beads, spawn workers, monitor progress, and close sessions, optionally using automation hooks.

What are the limitations of using a hub for bead orchestration?▼

Hub-based bead orchestration requires managing multiple parallel worker sessions, which can consume significant resources. You must manually handle per-project configuration and ensure proper session cleanup using wt close to avoid orphaned processes.