session-orchestrator

Name: session-orchestrator
Availability: InStock
Author: nexar

Orchestrate isolated Claude sessions in git worktrees for parallel execution and merging approved work to the main branch.

Updated Aug 27, 2026

Search Tags:#automation #git #claude #worktree #parallel #session #orchestrate

Ready to run

npx skills add https://github.com/getnexar/decrypt-tool --skill session-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-orchestrator
Source: https://github.com/getnexar/decrypt-tool/tree/main/ai-tools/skills/session-orchestrator
Command: npx skills add https://github.com/getnexar/decrypt-tool --skill session-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Orchestrates multiple Claude sessions in isolated worktrees to run independent tasks in parallel while preserving the main session context and avoiding cross-session data leakage.

Core Features & Use Cases

Dispatches work to isolated Claude sessions running in dedicated git worktrees.
Monitors session progress, surfaces questions to the user, and collects answers.
Merges approved work back into the main branch after internal reviews within each session.

Quick Start

Dispatch a batch of ready beads items to isolated sessions and monitor their progress.

Frequently Asked Questions about session-orchestrator

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

FAQPage Schema

How do I run isolated Claude sessions in parallel using git worktrees?▼

You can run isolated Claude sessions in parallel by dispatching independent tasks to dedicated git worktrees, which prevents cross-session data leakage and preserves the main session context. The orchestrator monitors each session and merges approved work back after internal reviews.

What is the best way to orchestrate multiple Claude automation tasks without context collision?▼

Orchestrating multiple Claude automation tasks without context collision is achieved by using isolated git worktrees for parallel execution. The system dispatches work, surfaces questions from sessions, and collects user answers to maintain safe, auditable collaboration.

How does merging approved work back to the main branch work after parallel session execution?▼

Merging approved work back to the main branch happens after each isolated session completes its internal review. The orchestrator ensures that only reviewed and approved changes from the parallel worktrees are integrated into the main branch.

Can I monitor progress and answer questions from multiple parallel Claude sessions in real time?▼

Yes, you can monitor progress and answer questions from parallel Claude sessions in real time. The orchestrator implements per-session buffers and status checks to surface questions to the user and collect answers while sessions run.

Do I need git worktrees to run parallel Claude sessions for independent tasks?▼

Yes, git worktrees are required to run parallel Claude sessions for independent tasks. They provide the isolated environments necessary to prevent cross-session data leakage and ensure safe, auditable collaboration across multiple execution contexts.