claude_swarm 0.1.16 → 0.1.18

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b71b3ce3aebae7de091dd130cda9fc4c474f538f444be15f1ee5b07501210db6
-  data.tar.gz: 846ac3f979b5912ccbc70f1810b760f625e75b1c7e905d5d1199b893d0bc3400
+  metadata.gz: 1aaf0eadabd67afb0bd79738de8c7fcbfb65887d477a2c0c002017cff9de15ec
+  data.tar.gz: 777f04c044a2204477d1328dc31b0b5361fa0007d0cf637254d3531260e3149d
 SHA512:
-  metadata.gz: 9f891010506baba80420357aad85a7fde6704c2ed99155e9cf32fd38cc35efd007ac19fe0e8a1df59b5f1df2d24980f7f0150551629667b42254d02bf77c4ddc
-  data.tar.gz: 29f913521f66298ee24dbdff1b8a043d3a00abe0723080b953cb3dbc127ac6e5ecb35a8b857f61af062db9d570f3c42a90e874dcb114b42f6bee163162f96a0a
+  metadata.gz: cb39225f7a1f4cfd7c0d7e0e3068ad5527473a04744ed0d18525b37452e7b7d4fe67c83f03fbb5c662591e51ed9c10a2360c5943676dc944ea83680652c977b7
+  data.tar.gz: 807b10f87678f4f49df363fbcc53bf3a71d14848adf2ebbad1d701737aad8f9ce6b894ebe7f6e84c45234a1f414ec1c1d171b79189090b6d6de2a71df00e05a7

data/CHANGELOG.md

@@ -1,3 +1,49 @@
+## [0.1.18]
+
+### Added
+- **Before commands**: Execute setup commands before launching the swarm
+  - New `before` field in swarm configuration accepts an array of commands
+  - Commands are executed in sequence before any Claude instances are launched
+  - All commands must succeed (exit code 0) for the swarm to launch
+  - Commands are only executed on initial launch, not when restoring sessions
+  - Output is logged to the session log file
+  - Useful for installing dependencies, starting services, or running setup scripts
+  - Example: `before: ["npm install", "docker-compose up -d"]`
+
+- **Git worktree support**: Run instances in isolated Git worktrees
+  - New `--worktree [NAME]` CLI option creates worktrees for all instances
+  - Worktrees are created inside each repository at `.worktrees/NAME`
+  - Each worktree gets its own branch (not detached HEAD) for proper Git operations
+  - Auto-generated names use session ID: `worktree-SESSION_ID`
+  - Per-instance worktree configuration in YAML:
+    - `worktree: true` - Use shared worktree name
+    - `worktree: false` - Disable worktree for this instance
+    - `worktree: "branch-name"` - Use custom worktree name
+  - Session restoration automatically restores worktrees
+  - Cleanup preserves worktrees with uncommitted changes or unpushed commits
+  - Warnings displayed when worktrees are preserved: "⚠️ Warning: Worktree has uncommitted changes"
+  - Multiple directories per instance work seamlessly with worktrees
+  - `.gitignore` automatically created in `.worktrees/` directory
+  - Example: `claude-swarm --worktree feature-branch`
+
+## [0.1.17]
+
+### Added
+- **Multi-directory support**: Instances can now access multiple directories
+  - The `directory` field in YAML configuration now accepts either a string (single directory) or an array of strings (multiple directories)
+  - Additional directories are passed to Claude using the `--add-dir` flag
+  - The first directory in the array serves as the primary working directory
+  - All specified directories must exist or validation will fail
+  - Example: `directory: [./frontend, ./backend, ./shared]`
+- **Session monitoring commands**: New commands for monitoring and managing active Claude Swarm sessions
+  - `claude-swarm ps`: List all active sessions with properly aligned columns showing session ID, swarm name, total cost, uptime, and directories
+  - `claude-swarm show SESSION_ID`: Display detailed session information including instance hierarchy and individual costs
+  - `claude-swarm watch SESSION_ID`: Tail session logs in real-time (uses native `tail -f`)
+  - `claude-swarm clean`: Remove stale session symlinks with optional age filtering (`--days N`)
+  - Active sessions are tracked via symlinks in `~/.claude-swarm/run/` for efficient monitoring
+  - Cost tracking aggregates data from `session.log.json` for accurate reporting
+  - Interactive main instance shows "n/a (interactive)" for cost when not available
+
 ## [0.1.16]
 
 ### Changed

data/CLAUDE.md

@@ -39,6 +39,47 @@ bundle exec rake release    # Release gem to RubyGems.org
 rake                  # Runs both tests and RuboCop
 ```
 
+## Git Worktree Support
+
+Claude Swarm supports launching instances in Git worktrees to isolate changes:
+
+### CLI Usage
+```bash
+# Create worktrees with custom name
+claude-swarm --worktree feature-branch
+
+# Create worktrees with auto-generated name (worktree-SESSION_ID)
+claude-swarm --worktree
+
+# Short form
+claude-swarm -w feature-x
+```
+
+### Per-Instance Configuration
+Instances can have individual worktree settings that override CLI behavior:
+
+```yaml
+instances:
+  main:
+    worktree: true         # Use shared worktree name (from CLI or auto-generated)
+  testing:
+    worktree: false        # Don't use worktree for this instance
+  feature:
+    worktree: "feature-x"  # Use specific worktree name
+  default:
+    # No worktree field - follows CLI behavior
+```
+
+### Worktree Behavior
+- Worktrees are created inside each repository in a `.worktrees/` directory
+- A `.gitignore` file is automatically created inside `.worktrees/` to ignore all contents
+- Each unique Git repository gets its own worktree with the same name
+- All instance directories are mapped to their worktree equivalents
+- Worktrees are automatically cleaned up when the swarm exits
+- Session metadata tracks worktree information for restoration
+- Non-Git directories are used as-is without creating worktrees
+- Existing worktrees with the same name are reused
+
 ## Architecture
 
 The gem is fully implemented with the following components:
@@ -49,6 +90,7 @@ The gem is fully implemented with the following components:
 - **ClaudeSwarm::Configuration** (`lib/claude_swarm/configuration.rb`): YAML parser and validator for swarm configurations
 - **ClaudeSwarm::McpGenerator** (`lib/claude_swarm/mcp_generator.rb`): Generates MCP JSON configurations for each instance
 - **ClaudeSwarm::Orchestrator** (`lib/claude_swarm/orchestrator.rb`): Launches the main Claude instance with proper configuration
+- **ClaudeSwarm::WorktreeManager** (`lib/claude_swarm/worktree_manager.rb`): Manages Git worktrees for isolated development
 
 ### Key Features
 
@@ -58,6 +100,7 @@ The gem is fully implemented with the following components:
 4. **Multiple MCP Types**: Supports both stdio and SSE MCP server types
 5. **Automatic MCP Generation**: Creates `.claude-swarm/` directory with MCP configs
 6. **Custom System Prompts**: Each instance can have a custom prompt via `--append-system-prompt`
+7. **Git Worktree Support**: Run instances in isolated Git worktrees with per-instance configuration
 
 ### How It Works
 
@@ -77,16 +120,20 @@ swarm:
   main: lead
   instances:
     lead:
+      description: "Lead developer coordinating the team"
       directory: .
       model: opus
       connections: [frontend, backend]
       prompt: "You are the lead developer coordinating the team"
       tools: [Read, Edit, Bash]
+      worktree: true  # Optional: use worktree for this instance
     frontend:
+      description: "Frontend developer specializing in React"
       directory: ./frontend
       model: sonnet
       prompt: "You specialize in frontend development with React"
       tools: [Edit, Write, Bash]
+      worktree: false  # Optional: disable worktree for this instance
 ```
 
 ## Testing
@@ -98,6 +145,7 @@ The gem includes comprehensive tests covering:
 - CLI command functionality
 - Session restoration
 - Vibe mode behavior
+- Worktree management and per-instance configuration
 
 ## Dependencies
 

data/README.md

@@ -1,10 +1,30 @@
 # Claude Swarm
 
-[![Gem Version](https://badge.fury.io/rb/claude_swarm.svg?cache_bust=0.1.15)](https://badge.fury.io/rb/claude_swarm)
+[![Gem Version](https://badge.fury.io/rb/claude_swarm.svg?cache_bust=0.1.17)](https://badge.fury.io/rb/claude_swarm)
 [![CI](https://github.com/parruda/claude-swarm/actions/workflows/ci.yml/badge.svg)](https://github.com/parruda/claude-swarm/actions/workflows/ci.yml)
 
 Claude Swarm orchestrates multiple Claude Code instances as a collaborative AI development team. It enables running AI agents with specialized roles, tools, and directory contexts, communicating via MCP (Model Context Protocol) in a tree-like hierarchy. Define your swarm topology in simple YAML and let Claude instances delegate tasks through connected instances. Perfect for complex projects requiring specialized AI agents for frontend, backend, testing, DevOps, or research tasks.
 
+## Table of Contents
+
+- [Installation](#installation)
+- [Prerequisites](#prerequisites)
+- [Usage](#usage)
+  - [Quick Start](#quick-start)
+  - [Configuration Format](#configuration-format)
+  - [MCP Server Types](#mcp-server-types)
+  - [Tools](#tools)
+  - [Examples](#examples)
+  - [Command Line Options](#command-line-options)
+  - [Session Monitoring](#session-monitoring)
+  - [Session Management and Restoration](#session-management-and-restoration-experimental)
+- [How It Works](#how-it-works)
+- [Troubleshooting](#troubleshooting)
+- [Architecture](#architecture)
+- [Development](#development)
+- [Contributing](#contributing)
+- [License](#license)
+
 ## Installation
 
 Install the gem by executing:
@@ -191,6 +211,10 @@ version: 1  # Required, currently only version 1 is supported
 swarm:
   name: "Swarm Name"  # Display name for your swarm
   main: instance_key  # Which instance to launch as the main interface
+  before:  # Optional: commands to run before launching the swarm
+    - "echo 'Setting up environment...'"
+    - "npm install"
+    - "docker-compose up -d"
   instances:
     # Instance definitions...
 ```
@@ -203,14 +227,15 @@ Each instance must have:
 
 Each instance can have:
 
-- **directory**: Working directory for this instance (can use ~ for home)
-- **model**: Claude model to use (opus, sonnet, haiku)
+- **directory**: Working directory for this instance (can use ~ for home). Can be a string for a single directory or an array of strings for multiple directories
+- **model**: Claude model to use (opus, sonnet)
 - **connections**: Array of other instances this one can communicate with
 - **allowed_tools**: Array of tools this instance can use (backward compatible with `tools`)
 - **disallowed_tools**: Array of tools to explicitly deny (takes precedence over allowed_tools)
 - **mcps**: Array of additional MCP servers to connect
 - **prompt**: Custom system prompt to append to the instance
 - **vibe**: Enable vibe mode (--dangerously-skip-permissions) for this instance (default: false)
+- **worktree**: Configure Git worktree usage for this instance (true/false/string)
 
 ```yaml
 instance_name:
@@ -336,7 +361,7 @@ swarm:
     database:
       description: "Database administrator managing data persistence"
       directory: ./db
-      model: haiku
+      model: sonnet
       allowed_tools:
         - Read
         - Bash
@@ -398,6 +423,72 @@ swarm:
         - Read
 ```
 
+#### Multi-Directory Support
+
+Instances can have access to multiple directories using an array (uses `claude --add-dir`):
+
+```yaml
+version: 1
+swarm:
+  name: "Multi-Module Project"
+  main: fullstack_dev
+  instances:
+    fullstack_dev:
+      description: "Full-stack developer working across multiple modules"
+      directory: [./frontend, ./backend, ./shared]  # Access to multiple directories
+      model: opus
+      allowed_tools: [Read, Edit, Write, Bash]
+      prompt: "You work across frontend, backend, and shared code modules"
+      
+    documentation_writer:
+      description: "Documentation specialist with access to code and docs"
+      directory: ["./docs", "./src", "./examples"]  # Multiple directories as array
+      model: sonnet
+      allowed_tools: [Read, Write, Edit]
+      prompt: "You maintain documentation based on code and examples"
+```
+
+When using multiple directories:
+- The first directory in the array is the primary working directory
+- Additional directories are accessible via the `--add-dir` flag in Claude
+- All directories must exist or the configuration will fail validation
+
+#### Before Commands
+
+You can specify commands to run before launching the swarm using the `before` field:
+
+```yaml
+version: 1
+swarm:
+  name: "Development Environment"
+  main: lead_developer
+  before:
+    - "echo '🚀 Setting up development environment...'"
+    - "npm install"
+    - "docker-compose up -d"
+    - "bundle install"
+  instances:
+    lead_developer:
+      description: "Lead developer coordinating the team"
+      directory: .
+      model: opus
+      allowed_tools: [Read, Edit, Write, Bash]
+```
+
+The `before` commands:
+- Are executed in sequence before launching any Claude instances
+- Must all succeed for the swarm to launch (exit code 0)
+- Are only executed on initial swarm launch, not when restoring sessions
+- Have their output logged to the session log file
+- Will abort the swarm launch if any command fails
+
+This is useful for:
+- Installing dependencies
+- Starting required services (databases, Docker containers, etc.)
+- Setting up the development environment
+- Running any prerequisite setup scripts
+
+
 #### Mixed Permission Modes
 
 You can have different permission modes for different instances:
@@ -429,6 +520,72 @@ swarm:
       allowed_tools: []  # Tools list ignored when vibe: true
 ```
 
+#### Git Worktrees
+
+Claude Swarm supports running instances in Git worktrees, allowing isolated work without affecting your main repository state. Worktrees are created inside each repository in a `.worktrees/` directory following Git best practices.
+
+**Example Structure:**
+```
+my-repo/
+├── .git/
+├── .worktrees/        (created by Claude Swarm)
+│   ├── .gitignore     (auto-created, contains "*")
+│   └── feature-x/     (worktree for feature-x branch)
+├── src/
+└── tests/
+```
+
+**CLI Option:**
+```bash
+# Create worktrees with auto-generated name (worktree-SESSION_ID)
+claude-swarm --worktree
+
+# Create worktrees with custom name
+claude-swarm --worktree feature-branch
+
+# Short form
+claude-swarm -w
+```
+
+**Per-Instance Configuration:**
+```yaml
+version: 1
+swarm:
+  name: "Worktree Example"
+  main: lead
+  instances:
+    lead:
+      description: "Lead developer"
+      directory: .
+      worktree: true  # Use shared worktree name from CLI (or auto-generate)
+      
+    testing:
+      description: "Test developer"  
+      directory: ./tests
+      worktree: false  # Don't use worktree for this instance
+      
+    feature_dev:
+      description: "Feature developer"
+      directory: ./features
+      worktree: "feature-x"  # Use specific worktree name
+```
+
+**Worktree Behavior:**
+- `worktree: true` - Uses the shared worktree name (from CLI or auto-generated)
+- `worktree: false` - Disables worktree for this instance
+- `worktree: "name"` - Uses a specific worktree name
+- Omitted - Follows CLI behavior (use worktree if `--worktree` is specified)
+
+**Notes:**
+- Worktrees are created inside each repository in a `.worktrees/` directory
+- Auto-generated worktree names use the session ID (e.g., `worktree-20241206_143022`)
+- This makes it easy to correlate worktrees with their Claude Swarm sessions
+- A `.gitignore` file is automatically created inside `.worktrees/` to ignore all worktree contents
+- All worktrees are automatically cleaned up when the swarm exits
+- Worktrees with the same name across different repositories share that name
+- Non-Git directories are unaffected by worktree settings
+- Existing worktrees with the same name are reused
+
 ### Command Line Options
 
 ```bash
@@ -450,9 +607,10 @@ claude-swarm --prompt "Fix the bug in the payment module"
 claude-swarm --session-id 20241206_143022
 claude-swarm --session-id ~/path/to/session
 
-# List available sessions
-claude-swarm list-sessions
-claude-swarm list-sessions --limit 20
+# Run all instances in Git worktrees
+claude-swarm --worktree                  # Auto-generated name (worktree-SESSION_ID)
+claude-swarm --worktree feature-branch   # Custom worktree name
+claude-swarm -w                          # Short form
 
 # Show version
 claude-swarm version
@@ -464,6 +622,67 @@ claude-swarm version
 claude-swarm mcp-serve INSTANCE_NAME --config CONFIG_FILE --session-timestamp TIMESTAMP
 ```
 
+### Session Monitoring
+
+Claude Swarm provides commands to monitor and inspect running sessions:
+
+```bash
+# List running swarm sessions with costs and uptime
+claude-swarm ps
+
+# Show detailed information about a session including instance hierarchy
+claude-swarm show 20250617_235233
+
+# Watch live logs from a session
+claude-swarm watch 20250617_235233
+
+# Watch logs starting from the last 50 lines
+claude-swarm watch 20250617_235233 -n 50
+
+# List all available sessions (including completed ones)
+claude-swarm list-sessions
+claude-swarm list-sessions --limit 20
+
+# Clean up stale session symlinks
+claude-swarm clean
+
+# Remove sessions older than 30 days
+claude-swarm clean --days 30
+```
+
+Example output from `claude-swarm ps`:
+```
+⚠️  Total cost does not include the cost of the main instance
+
+SESSION_ID       SWARM_NAME                 TOTAL_COST    UPTIME      DIRECTORY
+-------------------------------------------------------------------------------
+20250617_235233  Feature Development        $0.3847       15m         .
+20250617_143022  Bug Investigation          $1.2156       1h          ./shopify
+20250617_091547  Multi-Module Dev           $0.8932       30m         ./frontend, ./backend, ./shared
+```
+
+Note: The total cost shown reflects only the costs of connected instances called via MCP. The main instance cost is not tracked when running interactively.
+
+Example output from `claude-swarm show`:
+```
+Session: 20250617_235233
+Swarm: Feature Development
+Total Cost: $0.3847 (excluding main instance)
+Start Directory: /Users/paulo/project
+
+Instance Hierarchy:
+--------------------------------------------------
+├─ orchestrator [main] (orchestrator_e85036fc)
+   Cost: n/a (interactive) | Calls: 0
+   └─ test_archaeologist (test_archaeologist_c504ca5f)
+      Cost: $0.1925 | Calls: 1
+   └─ pr_analyst (pr_analyst_bfbefe56)
+      Cost: $0.1922 | Calls: 1
+
+Note: Main instance (orchestrator) cost is not tracked in interactive mode.
+      View costs directly in the Claude interface.
+```
+
 ### Session Management and Restoration (Experimental)
 
 Claude Swarm provides experimental session management with restoration capabilities. **Note: This feature is experimental and has limitations - the main instance's conversation context is not fully restored.**
@@ -502,10 +721,10 @@ Resume a previous session with all instances restored to their Claude session st
 
 ```bash
 # Resume by session ID
-claude-swarm --session-id 20241206_143022
+claude-swarm --session-id 20250617_143022
 
 # Resume by full path
-claude-swarm --session-id ~/.claude-swarm/sessions/my-project/20241206_143022
+claude-swarm --session-id ~/.claude-swarm/sessions/my-project/20250617_143022
 ```
 
 This will:

data/claude-swarm.yml

@@ -1,42 +1,14 @@
 version: 1
 swarm:
   name: "Swarm Name"
-  main: lead_developer
+  main: claude_swarm_architect
   instances:
-    lead_developer:
-      description: "Lead developer who coordinates the team and makes architectural decisions"
+    claude_swarm_architect:
+      description: "Lead architect"
       directory: .
-      model: sonnet
-      prompt: "You are the lead developer coordinating the team"
-      allowed_tools: [Read, Edit, Bash, Write]
-      connections: [frontend_dev, backend_dev]
+      model: opus
+      prompt: "You are an expert in Claude swarm architecture"
+      vibe: true
+      connections: [claudeception_architect]
 
-    # Example instances (uncomment and modify as needed):
-
-    frontend_dev:
-      description: "Frontend developer specializing in React and modern web technologies"
-      directory: .
-      model: sonnet
-      prompt: "You specialize in frontend development with React, TypeScript, and modern web technologies"
-      allowed_tools: [Read, Edit, Write, Bash]
-
-    backend_dev:
-      description: "Backend developer focusing on APIs, databases, and server architecture"
-      directory: .
-      model: sonnet
-      prompt: "You specialize in backend development, APIs, databases, and server architecture"
-      allowed_tools: [Read, Edit, Write, Bash]
-
-    # devops_engineer:
-    #   description: "DevOps engineer managing infrastructure, CI/CD, and deployments"
-    #   directory: .
-    #   model: sonnet
-    #   prompt: "You specialize in infrastructure, CI/CD, containerization, and deployment"
-    #   allowed_tools: [Read, Edit, Write, Bash]
-
-    # qa_engineer:
-    #   description: "QA engineer ensuring quality through comprehensive testing"
-    #   directory: ./tests
-    #   model: sonnet
-    #   prompt: "You specialize in testing, quality assurance, and test automation"
-    #   allowed_tools: [Read, Edit, Write, Bash]
+    

data/examples/monitoring-demo.yml

@@ -0,0 +1,26 @@
+version: 1
+swarm:
+  name: "Monitoring Demo"
+  main: coordinator
+  instances:
+    coordinator:
+      description: "Main coordinator managing the team"
+      directory: .
+      model: haiku
+      connections: [analyzer, reporter]
+      prompt: "You coordinate analysis and reporting tasks"
+      allowed_tools: [Read, Edit]
+    
+    analyzer:
+      description: "Data analyzer processing information"
+      directory: ./data
+      model: haiku  
+      prompt: "You analyze data and provide insights"
+      allowed_tools: [Read, Bash]
+    
+    reporter:
+      description: "Report generator creating summaries"
+      directory: ./reports
+      model: haiku
+      prompt: "You generate reports from analysis"
+      allowed_tools: [Write, Edit]

data/examples/multi-directory.yml

@@ -0,0 +1,26 @@
+version: 1
+swarm:
+  name: "Multi-Directory Example"
+  main: fullstack_dev
+  instances:
+    fullstack_dev:
+      description: "Full-stack developer with access to multiple project directories"
+      directory: [./frontend, ./backend, ./shared, ./docs]
+      model: opus
+      connections: [frontend_specialist, backend_specialist]
+      allowed_tools: [Read, Edit, Write, Bash, WebSearch]
+      prompt: "You are a full-stack developer with access to frontend, backend, shared code, and documentation directories"
+      
+    frontend_specialist:
+      description: "Frontend developer focused on React components"
+      directory: ./frontend
+      model: sonnet
+      allowed_tools: [Read, Edit, Write, Bash]
+      prompt: "You specialize in React and frontend development"
+      
+    backend_specialist:
+      description: "Backend developer focused on API development"
+      directory: ./backend
+      model: sonnet
+      allowed_tools: [Read, Edit, Write, Bash]
+      prompt: "You specialize in backend API development"

data/examples/with-before-commands.yml

@@ -0,0 +1,30 @@
+version: 1
+swarm:
+  name: "Development Environment"
+  main: lead_developer
+  before:
+    - "echo '🚀 Setting up development environment...'"
+    - "echo '📦 Installing dependencies...'"
+    - "echo '🐳 Starting Docker containers...'"
+  instances:
+    lead_developer:
+      description: "Lead developer who coordinates the team"
+      directory: .
+      model: sonnet
+      prompt: "You are the lead developer coordinating the team"
+      allowed_tools: [Read, Edit, Bash, Write]
+      connections: [frontend_dev, backend_dev]
+    
+    frontend_dev:
+      description: "Frontend developer specializing in React"
+      directory: ./frontend
+      model: sonnet
+      prompt: "You specialize in frontend development with React"
+      allowed_tools: [Read, Edit, Write]
+    
+    backend_dev:
+      description: "Backend developer focusing on APIs"
+      directory: ./backend
+      model: sonnet
+      prompt: "You specialize in backend development and APIs"
+      allowed_tools: [Read, Edit, Write, Bash]

data/lib/claude_swarm/claude_code_executor.rb

@@ -12,8 +12,9 @@ module ClaudeSwarm
 
     def initialize(working_directory: Dir.pwd, model: nil, mcp_config: nil, vibe: false,
                    instance_name: nil, instance_id: nil, calling_instance: nil, calling_instance_id: nil,
-                   claude_session_id: nil)
+                   claude_session_id: nil, additional_directories: [])
       @working_directory = working_directory
+      @additional_directories = additional_directories
       @model = model
       @mcp_config = mcp_config
       @vibe = vibe
@@ -259,6 +260,12 @@ module ClaudeSwarm
 
       cmd_array << "--verbose"
 
+      # Add additional directories with --add-dir
+      cmd_array << "--add-dir" if @additional_directories.any?
+      @additional_directories.each do |additional_dir|
+        cmd_array << additional_dir
+      end
+
       # Add MCP config if specified
       cmd_array += ["--mcp-config", @mcp_config] if @mcp_config
 

data/lib/claude_swarm/claude_mcp_server.rb

@@ -28,7 +28,8 @@ module ClaudeSwarm
         instance_id: instance_config[:instance_id],
         calling_instance: calling_instance,
         calling_instance_id: calling_instance_id,
-        claude_session_id: instance_config[:claude_session_id]
+        claude_session_id: instance_config[:claude_session_id],
+        additional_directories: instance_config[:directories][1..] || []
       )
 
       # Set class variables so tools can access them