claude_swarm 0.1.15 → 0.1.17

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: dc1ac6dbcc7eac54e907f574c827580275e147e42e92122d467809addb614ae9
-  data.tar.gz: d579b2a49bc0323c4704736597c1d3a9bf8e24a29c0bfe63bd21969560b4dbf9
+  metadata.gz: 3f0ab99665f31bddf2d3641525481ce2df55e910950af03290137246847bf70d
+  data.tar.gz: 2435170f5b61604c3131b1680f60ed8727795c58432806d9b61007813d4f5ce3
 SHA512:
-  metadata.gz: 20398e7167acc7f88c611da67a0d613fbfba9e225701c5dd1681f2a2ffac12bd81bbf9e4463c45564df0046edd17f3a299edbfedd1c79b0a463127c53853283f
-  data.tar.gz: be84c91452a5cc0e00ec725e9e4f3a75b8e4b94f72438a796a3a6e8f787c4c8a2c46ad857bb661c50971c2fda25ca51fe2e25fc650c3025001292dba054f293b
+  metadata.gz: ee74c188f6cc7fd31bb8705661f0913674bb687fd1eae6c2973728d2418f62bbad86054a89bd150965f39ec0bbd37ac04b2413dd22340311afd03cd5ec9d5424
+  data.tar.gz: a6c5fb7db4a8659619c9c7b5de000303ce91b046b85d635381f437adc92b4fd739e8d2142f0e65323346d1ba4d2607bf2b90c7d76fcf7c119bf6b9d5c431a7fc

data/CHANGELOG.md

@@ -1,3 +1,46 @@
+## [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
+- **Breaking change**: Removed custom permission MCP server in favor of Claude's native `mcp__MCP_NAME` pattern
+- Connected instances are now automatically added to allowed tools as `mcp__<instance_name>`
+- CLI parameter `--tools` renamed to `--allowed-tools` for consistency with YAML configuration
+- MCP generator no longer creates permission MCP server configurations
+
+### Removed
+- Removed `PermissionMcpServer` and `PermissionTool` classes
+- Removed `tools-mcp` CLI command
+- Removed regex tool pattern syntax - use Claude Code patterns instead
+- Removed `--permission-prompt-tool` flag from orchestrator
+- Removed permission logging to `permissions.log`
+
+### Migration Guide
+- Replace custom tool patterns with Claude Code's native patterns in your YAML files:
+  - `"Bash(npm:*)"` → Use `Bash` and Claude Code's built-in command restrictions
+  - `"Edit(*.js)"` → Use `Edit` and Claude Code's built-in file restrictions
+- For fine-grained tool control, use Claude Code's native patterns:
+  - `mcp__<server_name>__<tool_name>` for specific tools from an MCP server
+  - `mcp__<server_name>` to allow all tools from an MCP server
+- Connected instances are automatically accessible via `mcp__<instance_name>` pattern
+- See Claude Code's documentation for full details on supported tool patterns
+
 ## [0.1.15]
 
 ### Changed

data/CLAUDE.md

@@ -54,7 +54,7 @@ The gem is fully implemented with the following components:
 
 1. **YAML Configuration**: Define swarms with instances, connections, tools, and MCP servers
 2. **Inter-Instance Communication**: Instances connect via MCP using `claude mcp serve` with `-p` flag
-3. **Tool Restrictions**: Support for pattern-based tool restrictions (e.g., `Bash(npm:*)`)
+3. **Tool Restrictions**: Support for tool restrictions using Claude's native pattern (connections are available as `mcp__instance_name`)
 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`
@@ -63,9 +63,10 @@ The gem is fully implemented with the following components:
 
 1. User creates a `claude-swarm.yml` file defining the swarm topology
 2. Running `claude-swarm` parses the configuration and validates it
-3. MCP configuration files are generated for each instance in `.claude-swarm/`
+3. MCP configuration files are generated for each instance in a session directory
 4. The main instance is launched with `exec`, replacing the current process
 5. Connected instances are available as MCP servers to the main instance
+6. When an instance has connections, those connections are automatically added to its allowed tools as `mcp__<connection_name>`
 
 ### Configuration Example
 
@@ -85,15 +86,18 @@ swarm:
       directory: ./frontend
       model: sonnet
       prompt: "You specialize in frontend development with React"
-      tools: [Edit, Write, "Bash(npm:*)"]
+      tools: [Edit, Write, Bash]
 ```
 
 ## Testing
 
-The gem includes basic tests for version number and CLI existence. Additional tests should be added for:
+The gem includes comprehensive tests covering:
 - Configuration parsing and validation
-- MCP generation logic
+- MCP generation logic with connections
 - Error handling scenarios
+- CLI command functionality
+- Session restoration
+- Vibe mode behavior
 
 ## Dependencies
 

data/README.md

@@ -1,6 +1,6 @@
 # Claude Swarm
 
-[![Gem Version](https://badge.fury.io/rb/claude_swarm.svg?cache_bust=0.1.14)](https://badge.fury.io/rb/claude_swarm)
+[![Gem Version](https://badge.fury.io/rb/claude_swarm.svg?cache_bust=0.1.15)](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.
@@ -113,7 +113,7 @@ swarm:
       directory: ./web-frontend/src
       model: opus
       prompt: "You specialize in React components and state management"
-      allowed_tools: [Edit, Write, "Bash(npm:*)"]
+      allowed_tools: [Edit, Write, Bash]
     
     css_expert:
       description: "CSS specialist handling styling and responsive design"
@@ -142,7 +142,7 @@ swarm:
       directory: ./api-server/db
       model: opus
       prompt: "You handle database schema and migrations"
-      allowed_tools: [Edit, Write, "Bash(psql:*, migrate:*)"]
+      allowed_tools: [Edit, Write, Bash]
     
     mobile_lead:
       description: "Mobile team lead coordinating cross-platform development"
@@ -157,21 +157,21 @@ swarm:
       directory: ./mobile-app/ios
       model: opus
       prompt: "You develop the iOS application"
-      allowed_tools: [Edit, Write, "Bash(xcodebuild:*, pod:*)"]
+      allowed_tools: [Edit, Write, Bash]
     
     android_dev:
       description: "Android developer creating native Android apps"
       directory: ./mobile-app/android
       model: opus
       prompt: "You develop the Android application"
-      allowed_tools: [Edit, Write, "Bash(gradle:*, adb:*)"]
+      allowed_tools: [Edit, Write, Bash]
     
     devops:
       description: "DevOps engineer managing CI/CD and infrastructure"
       directory: ./infrastructure
       model: opus
       prompt: "You handle CI/CD and infrastructure"
-      allowed_tools: [Read, Edit, "Bash(docker:*, kubectl:*)"]
+      allowed_tools: [Read, Edit, Bash]
 ```
 
 In this setup:
@@ -179,6 +179,7 @@ In this setup:
 - Each team lead can work with their specialized developers
 - Each instance is independent - connections create separate MCP server instances
 - Teams work in isolated directories with role-appropriate tools
+- Connected instances are accessible via MCP tools like `mcp__frontend_lead__task`, `mcp__backend_lead__task`, etc.
 
 
 ### Configuration Format
@@ -202,8 +203,8 @@ 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)
@@ -272,23 +273,22 @@ allowed_tools:
   - WebFetch       # Fetch web content
   - WebSearch      # Search the web
 
-disallowed_tools:  # Optional: explicitly deny specific tools
-  - "Write(*.md)"  # Don't allow writing markdown files
-  - "Bash(rm:*)"   # Don't allow rm commands
+# Note: Pattern-based tool restrictions have been deprecated.
+# Use allowed_tools and disallowed_tools with tool names only.
 ```
 
 Tools are passed to Claude using the `--allowedTools` and `--disallowedTools` flags with comma-separated values. Disallowed tools take precedence over allowed tools.
 
-#### Tool Restrictions
-
-You can restrict tools with pattern-based filters:
+#### Available Tools
 
 ```yaml
 allowed_tools:
-  - Read                    # Unrestricted read access
-  - Edit                    # Unrestricted edit access
-  - "Bash(npm:*)"          # Only allow npm commands
-  - "Bash(git:*, make:*)"  # Only allow git and make commands
+  - Read          # File reading
+  - Edit          # File editing
+  - Write         # File creation
+  - Bash          # Command execution
+  - WebFetch      # Fetch web content
+  - WebSearch     # Search the web
 ```
 
 ### Examples
@@ -336,7 +336,7 @@ swarm:
     database:
       description: "Database administrator managing data persistence"
       directory: ./db
-      model: haiku
+      model: sonnet
       allowed_tools:
         - Read
         - Bash
@@ -398,6 +398,36 @@ 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
+
 #### Mixed Permission Modes
 
 You can have different permission modes for different instances:
@@ -419,7 +449,7 @@ swarm:
       description: "Worker with restricted permissions"
       directory: ./sensitive
       model: sonnet
-      allowed_tools: [Read, "Bash(ls:*)"]  # Only allow read and ls commands
+      allowed_tools: [Read, Bash]  # Allow read and bash commands
       
     trusted_worker:
       description: "Trusted worker with more permissions"
@@ -450,21 +480,77 @@ 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
-
 # Show version
 claude-swarm version
 
-# Start permission MCP server (for testing/debugging)
-claude-swarm tools-mcp --allowed-tools 'mcp__frontend__*,mcp__backend__*'
-claude-swarm tools-mcp --allowed-tools 'Read,Edit' --disallowed-tools 'Edit(*.log)'
+# Note: The permission MCP server has been deprecated. 
+# Tool permissions are now handled through allowed_tools and disallowed_tools in your configuration.
 
 # Internal command for MCP server (used by connected instances)
 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.**
@@ -477,7 +563,7 @@ All session files are organized in `~/.claude-swarm/sessions/{project}/{timestam
 - `{instance_name}.mcp.json`: MCP configuration files
 - `session.log`: Human-readable request/response tracking
 - `session.log.json`: All events in JSONL format (one JSON per line)
-- `permissions.log`: Permission checks and decisions
+# Note: permissions.log is no longer generated as the permission MCP server has been deprecated
 
 #### Listing Sessions
 View your previous Claude Swarm sessions:
@@ -503,10 +589,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:
@@ -535,15 +621,11 @@ This will:
 2. **MCP Generation**: For each instance, it generates an MCP configuration file that includes:
    - Any explicitly defined MCP servers
    - MCP servers for each connected instance (using `claude-swarm mcp-serve`)
-   - A permission MCP server (unless using `--vibe` mode)
-3. **Tool Permissions**: Claude Swarm automatically manages tool permissions:
-   - Each instance's configured tools are allowed via the permission MCP
-   - Supports wildcard patterns (e.g., `mcp__frontend__*` allows all frontend MCP tools)
+3. **Tool Permissions**: Claude Swarm manages tool permissions through configuration:
+   - Each instance's `allowed_tools` specifies which tools it can use
+   - Connected instances are accessible via `mcp__<instance_name>__*` pattern
    - Disallowed tools take precedence over allowed tools for fine-grained control
-   - Eliminates the need to manually accept each tool or use global `--vibe` mode
    - Per-instance `vibe: true` skips all permission checks for that specific instance
-   - The permission MCP uses `--permission-prompt-tool` to check tool access
-   - Permission decisions are logged to `~/.claude-swarm/sessions/{project}/{timestamp}/permissions.log`
 4. **Session Persistence**: Claude Swarm automatically tracks session state:
    - Generates a shared session path for all instances
    - Each instance's Claude session ID is captured and saved

data/claude-swarm.yml

@@ -1,42 +1,26 @@
 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"
-      directory: .
-      model: sonnet
-      prompt: "You are the lead developer coordinating the team"
-      allowed_tools: [Read, Edit, Bash, Write]
-      connections: [frontend_dev, backend_dev]
+    claude_swarm_architect:
+      description: "Lead architect"
+      directory:
+        - .
+        - /Users/paulo/src/github.com/shopify-playground/claudeception
+      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(npm:*)", "Bash(yarn:*)", "Bash(pnpm:*)"]
+    claudeception_architect:
+      description: "You are an expert in Claudeception architecture"
+      directory:
+        - .
+        - /Users/paulo/src/github.com/shopify-playground/claudeception
+      model: opus
+      prompt: "You are an expert in Claudeception architecture"
+      vibe: true
 
-    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(docker:*)", "Bash(kubectl:*)", "Bash(terraform:*)"]
-
-    # 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/example/microservices-team.yml

@@ -58,7 +58,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(npm:*, yarn:*, jest:*)"
+        - Bash
     
     ui_designer:
       description: "UI/UX specialist creating responsive designs and managing design system"
@@ -91,7 +91,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(go:*, docker:*, make:*)"
+        - Bash
     
     api_gateway_dev:
       description: "API gateway developer managing request routing and rate limiting"
@@ -101,7 +101,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(go:*, docker:*, kong:*)"
+        - Bash
     
     core_service_dev:
       description: "Core business logic service developer"
@@ -111,7 +111,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(python:*, pip:*, pytest:*, docker:*)"
+        - Bash
     
     shared_lib_dev:
       description: "Shared libraries developer maintaining common code across services"
@@ -122,7 +122,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(npm:*, go:*, python:*)"
+        - Bash
     
     # Mobile Team
     mobile_lead:
@@ -143,7 +143,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(swift:*, xcodebuild:*, pod:*, fastlane:*)"
+        - Bash
     
     android_senior:
       description: "Senior Android developer creating Kotlin applications"
@@ -153,7 +153,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(gradle:*, adb:*, fastlane:*)"
+        - Bash
     
     # Data Team
     data_lead:
@@ -175,7 +175,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(python:*, airflow:*, spark:*, dbt:*)"
+        - Bash
     
     ml_engineer:
       description: "ML engineer developing and deploying machine learning models"
@@ -185,7 +185,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(python:*, jupyter:*, mlflow:*, docker:*)"
+        - Bash
     
     analytics_dev:
       description: "Analytics developer creating dashboards and reports"
@@ -195,7 +195,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(python:*, sql:*)"
+        - Bash
     
     # DevOps & Infrastructure
     devops_lead:
@@ -217,7 +217,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(kubectl:*, helm:*, prometheus:*, grafana:*)"
+        - Bash
     
     platform_engineer:
       description: "Platform engineer managing Kubernetes and container infrastructure"
@@ -227,7 +227,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(kubectl:*, helm:*, docker:*, istioctl:*)"
+        - Bash
     
     cloud_architect:
       description: "Cloud architect managing AWS/GCP infrastructure and costs"
@@ -237,7 +237,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(terraform:*, aws:*, gcloud:*)"
+        - Bash
     
     # Quality & Security
     qa_lead:
@@ -259,7 +259,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(npm:*, cypress:*, playwright:*)"
+        - Bash
     
     backend_qa:
       description: "Backend QA engineer creating API tests and integration tests"
@@ -269,7 +269,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(python:*, pytest:*, postman:*, k6:*)"
+        - Bash
     
     mobile_qa:
       description: "Mobile QA engineer testing iOS and Android applications"
@@ -279,7 +279,7 @@ swarm:
       allowed_tools:
         - Edit
         - Write
-        - "Bash(appium:*, xctest:*, espresso:*)"
+        - Bash
     
     security_lead:
       description: "Security lead ensuring application and infrastructure security"
@@ -290,4 +290,4 @@ swarm:
       allowed_tools:
         - Read
         - Edit
-        - "Bash(trivy:*, snyk:*, owasp:*)"
+        - Bash

data/example/test-generation.yml

@@ -70,7 +70,7 @@ swarm:
         - Read
         - Edit
         - Write
-        - "Bash(bundle:*)"
+        - Bash
 
     integration_test_expert:
       description: "Integration test specialist for controllers, API endpoints, and request specs"
@@ -111,7 +111,7 @@ swarm:
         - Read
         - Edit
         - Write
-        - "Bash(bundle:*, rails:*)"
+        - Bash
 
     system_test_expert:
       description: "System test specialist for end-to-end user flows and JavaScript interactions"
@@ -154,7 +154,7 @@ swarm:
         - Read
         - Edit
         - Write
-        - "Bash(bundle:*)"
+        - Bash
 
     factory_specialist:
       description: "Test data specialist managing factories, traits, and test data generation"
@@ -198,7 +198,7 @@ swarm:
         - Read
         - Edit
         - Write
-        - "Bash(bundle:*)"
+        - Bash
 
     test_quality_reviewer:
       description: "Test quality assurance specialist ensuring best practices, coverage, and maintainability"
@@ -243,4 +243,4 @@ swarm:
         Provide actionable feedback to improve test quality and coverage.
       allowed_tools:
         - Read
-        - "Bash(bundle:*, rubocop:*)"
+        - 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]